Loading ...

REST API: Create Bookmark | Axero Documentation

Home » axero documentation » Wiki » Documentation » REST API Overview » REST API: Content » REST API: Bookmarks » REST API: Create Bookmark
Axero Documentation  Wiki
Public Space
Activity Stream Content
Version 24

REST API: Create Bookmark

0 
 /5
0 (0votes)
Open API Guide
POST/api/content/{ContentID}/bookmarks

Creates a bookmark of content

Request

Request Header

HeaderRequiredValueDescription
AuthorizationYESBearer YOUR_TOKENBearer token for the authenticated user. Learn how to create Bearer tokens
Content-TypeYESapplication/jsonMust be set to application/json

Required Parameters

ParameterTypeRequiredLocationDescription
ContentIDIntegerYESPathUnique identifier for particular content
TitleStringYESBodyDisplay name for the bookmark shown in the user's bookmarks list.
DescriptionStringYESBodyOptional note or context saved with the bookmark for future reference.
EntityTypeStringYESBodyREST API: System Entity Types Refers to the entity type id of the content

Example

Request Header

Authorization: Bearer YOUR_TOKEN
Content-Type: application/json

Request URL

https://your-site.com/api/content/123/bookmarks

Request Body

{
  "Title": "Blogging",
  "Description": "Article on blogging",
  "Entitytype": 3
}

Success Response

{
  "IsError": false,
  "ResponseMessage": "",
  "ResponseData": 22
}

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. (contentID, bookmark)Verify the request payload against the required parameters
401 UnauthorizedMissing or invalid Bearer tokenCheck token validity. Learn how to create Bearer tokens →
403 ForbiddenUser does not have sufficient permissionsConfirm the user has the required roles for this action
404 Not FoundThe specified content was not found.Verify the contentID is correct.
500 Server ErrorInternal failureRetry 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