Loading ...

REST API: Update Content Multiple | Axero Documentation

Home » axero documentation » Wiki » Documentation » REST API Overview » REST API: Content » REST API: Update Content Multiple
Axero Documentation  Wiki
Public Space
Activity Stream Content
Version 52

REST API: Update Content Multiple

0 
 /5
0 (0votes)
Open API Guide
PUT/api/content/multiple

You can update existing multiple contents in a single request. For example, set the expiration dates of multiple articles at once.

Request

Request Header

Header Required Value Description
Authorization YES Bearer YOUR_TOKEN Bearer token for the authenticated user. Learn how to create Bearer tokens.
Content-Type YES application/json Must be set to application/json

Required Parameters

Parameter Type Required Location Description
ContentID Integer YES Body Unique identifier for content. List of supported entities: Articles, Blogs, CMS Pages, Wikis, Ideas, Photos, Albums, Files, Forums, Forum Groups, Forum Topics, Forum Posts
Content JSON String YES Body This is JSON that represents a content object that you're updating. This should be of the format seen below in the sample given.

Optional Parameters

Parameter Type Required Location Description
ContentTitle String NO Body Content Title of the entity to be updated
ContentSummary String NO Body Content Summary of Articles, Blogs or Videos to be updated
ContentBody String NO Body Content Body of the entity to be updated
CategoryID Integer NO Body CategoryID for Articles, Blogs, CMSPage or Ideas to be updated
ParentContentID Integer NO Body Used in Wikis, Forums, Forum Topics, Forum Posts to specify the parent content under which this content is updated
ContentStageID Integer NO Body Used in Ideas to specify Idea stage
AuthorID Integer NO Body Author's unique ID. It can be used for ghostwriting purposes, allowing content to be attributed to different authors as needed.
IsFeatured Boolean NO Body Used to mark content as "featured".true= Set the content as featured
StatusID Integer NO Body Enter number for corresponding status: 1 - Published, 2 - Draft, 5 - Expired 
IsContentAvailablePostExpiry Boolean NO Body Used to indicate if content will be visable after exipration date.true= content will be visable after expiration date
DateExpired String NO Body Used to update expiration date of content. Applies to all supported entities except Files.UTC Time format required (24HR): YYYY-MM-DDTHH:MM:SSZ
DateExpiredISOString String NO Body Used to update the expiration date of File entities only. For all other content types, use DateExpired instead.UTC Time format required (24HR): YYYY-MM-DDTHH:MM:SSZ

Notes

  • If changing status to 5 (Expired), you must include a DateExpired (or DateExpiredISOString for files) property along with it.
  • If putting DateExpired (or DateExpiredISOString for files) on content in a space where "Content Expiration" is not enabled in settings, the content will still have the new expiration date as a part of the content, but the date will not be visible unless the setting is enabled.

Examples

Example 1

Request Header

Authorization: Bearer YOUR_TOKEN
Content-Type: application/json

Request URL

https://your-site.com/api/content/multiple

Request Body

[
  {
    "ContentID": 9740,
    "ContentTitle": "Jupiter is the fifth planet from the Sun",
    "ContentBody": "Jupiter is primarily composed of hydrogen with a quarter of its mass being helium, although helium only comprises about a tenth of the number of molecules. It may also have a rocky core of heavier elements, but like the other giant planets, Jupiter lacks a well-defined solid surface."
  },
  {
    "ContentID": 9739,
    "ContentTitle": "Lorem ipsum dolor sit amet",
    "ContentBody": "Enim praesent elementum facilisis leo vel. Lorem mollis aliquam ut porttitor leo a diam sollicitudin tempor. Lobortis scelerisque fermentum dui faucibus in."
  },
  {
    "ContentID": 8763,
    "ContentTitle": "Mauris in aliquam sem fringilla ut morbi",
    "ContentBody": "Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. At in tellus integer feugiat."
  },
  {
    "ContentID": 9741,
    "ContentTitle": "Adipiscing commodo elit at imperdiet dui accumsan sit amet nulla",
    "ContentBody": "Sed arcu non odio euismod. Dolor sed viverra ipsum nunc aliquet bibendum enim facilisis gravida."
  }
]

Success Response

[
  {
    "IsError": false,
    "ResponseMessage": "The content is published.",
    "ResponseData": 9740
  },
  {
    "IsError": false,
    "ResponseMessage": "The content is published.",
    "ResponseData": 9739
  },
  {
    "IsError": false,
    "ResponseMessage": "The content is published.",
    "ResponseData": 8763
  },
  {
    "IsError": false,
    "ResponseMessage": "The content is published.",
    "ResponseData": 9741
  }
]

Example 2

Request Body

[
  {
    "ContentID": 7999,
    "StatusID": 5,
    "IsContentAvailablePostExpiry": true,
    "DateExpired": "2026-12-21T06:30:00Z"
  },
  {
    "ContentID": 7998,
    "StatusID": 5,
    "IsContentAvailablePostExpiry": true,
    "DateExpired": "2026-12-21T06:30:00Z"
  },
  {
    "ContentID": 7995,
    "StatusID": 5,
    "IsContentAvailablePostExpiry": true,
    "DateExpired": "2026-12-21T06:30:00Z"
  },
  {
    "ContentID": 9741,
    "StatusID": 5,
    "IsContentAvailablePostExpiry": false,
    "DateExpired": "2026-12-21T06:30:00Z"
  }
]

Response

[
  {
    "IsError": false,
    "ResponseMessage": "Expired.",
    "ResponseData": 7999
  },
  {
    "IsError": false,
    "ResponseMessage": "Expired.",
    "ResponseData": 7998
  },
  {
    "IsError": false,
    "ResponseMessage": "Expired.",
    "ResponseData": 7995
  },
  {
    "IsError": false,
    "ResponseMessage": "Expired.",
    "ResponseData": 9741
  }
]

Error Response

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

Error Handling

Status Code Likely Cause Next Action
400 Bad Request One or more required fields are missing or invalid. (source) Verify the request payload against the required parameters.
401 Unauthorized Missing or invalid Bearer token. Check token validity. Learn how to create Bearer tokens →
403 Forbidden User does not have sufficient permissions. Confirm the user has the required roles for this action.
404 Not Found The specified content was not found. Verify the contentID is correct.
500 Server Error Internal 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