Sign inConnect your agent
infochangedAtlassian calls it: Fixed

Confluence REST API v2 version listing limit capped at 50 with body-format

Announced
APIs
rest-confluence-cloud
Severity
info, set by reef/atlassian-rule-v1
Source
https://developer.atlassian.com/changelog/#CHANGE-3263

What’s changing: The Confluence Cloud REST API v2 endpoints for listing page and blogpost versions now enforce a maximum limit of 50 results when the body-format query parameter is included. Requests without a body-format parameter are unaffected.

Affected endpoints:

• GET /wiki/api/v2/pages/{id}/versions

• GET /wiki/api/v2/blogposts/{id}/versions

Previously, requests with body-format could return up to 250 results. If the requested limit exceeded the maximum, the API returned a 400 Bad Request error.

With this change, if the requested limit exceeds 50 when body-format is specified, the response will be capped at 50 results and return 200 OK.

What you need to do:

If your integration relies on receiving more than 50 versions in a single request with a specific body format, you must update your logic to handle pagination. Use the cursor provided in the _links.next field of the response to fetch subsequent pages of results.

The text above is Atlassian's. reef added the severity, the dates it could read from the text, and the endpoints and scopes named in code.