Loading ...

REST API: Get Required Reading | Axero Documentation

Home » axero documentation » Wiki » Documentation » REST API Overview » REST API: Content » REST API: Get Required Reading
Axero Documentation  Wiki
Public Space
Activity Stream Content
Version 21

REST API: Get Required Reading

0 
 /5
0 (0votes)
Open API Guide
GET/api/content/required

Used to get the required reading content for user.

Request

Request Header

HeaderRequiredValueDescription
AuthorizationYESBearer YOUR_TOKENBearer token for the authenticated user. Learn how to create Bearer tokens.

Optional Parameters

ParameterTypeRequiredLocationDescription
SpaceIDIntegerNOQueryID of the space under which the content exists
EntityTypeIDIntegerNOQueryID of the entity type. See REST API: System Entity Types 
LogViewBooleanNOQueryLogs the API call as an action in User Activity when set to true
StartPageIntegerNOQuerySpecifies the starting page of the required reading list to be returned
PageLengthIntegerNOQuerySpecifies the number of results to be returned per page

Example

Request Header

Authorization: Bearer YOUR_TOKEN

Request URL

https://your-site.com/Assets/Uploaded-Photos/625/292606e0-01e4-4df8-86dd-2ca1d96f6446.jpeg

Success Response

{
  "IsError": false,
  "ResponseMessage": "",
  "ResponseData": [
    {
      "ContentID": 9481,
      "EntityType": 14,
      "ContentTypeID": 14,
      "ContentTitle": "Lorem Files.pdf",
      "ContentStub": "lorem-files-pdf",
      "ContentBody": "

Error Response

{
  "IsError": true,
  "ResponseMessage": "Required parameter is missing or invalid.",
  "ResponseData": null
}

Error Handling

Status CodeLikely CauseNext Action
400 Bad RequestOne or more required fields are missing or invalid.Verify the request payload against the required parameters.
401 UnauthorizedMissing or invalid Bearer token.Check token validity. Learn how to create Bearer tokens →
403 ForbiddenUser does not have sufficient permissions.Confirm the user has the required roles for this action.
500 Server ErrorInternal failure.Retry later.

Rate Limits

While Axero does not enforce hard rate limits by default, we recommend the following best practices to ensure optimal performance:

  • Sustained Request Rate: Do not exceed 5 API calls per second
  • Sequential Processing: Wait for each request to complete before sending the next in automated workflows
  • Concurrent Connections: If parallel processing is required, limit to 3 or fewer simultaneous requests
  • Response Timeout: Ensure API responses complete within 15 seconds during testing

Axero may implement temporary rate restrictions if excessive API usage affects overall site performance. For high-volume integrations, contact Axero to discuss your requirements.

Wiki Index

Pages