Hi,
Requesting a page with its children, for example:
/wiki/rest/api/content/1185808839/child/page
I get the lists with next links, here is a snippet from a response from you (confluence cloud API) just a few minutes ago, for example:
start: 0,
limit: 25,
size: 25,
_links: {
base: "https://HOSTXXX/wiki",
context: "/wiki",
next: "/rest/api/content/1185808839/child/page?next=true&limit=25&start=25",
self: "https://HOSTXXX/wiki/rest/api/content/1185808839/child/page"
}
The next link you provide in this API response is broken, does not work. It returns a 404:
<status>
<status-code>404</status-code>
<message>null for uri: https://HOSTXXXX/rest/api/content/1185808839/child/page?next=true&limit=25&start=25</message>
</status>
this has worked for a long time and worked a few weeks ago, trying this today Sept 9th it does not. Other requests work as expected.
I have searched and looked through changes to the API, the only related thing I could find is the change to cursors, but in that note it clearly said that following the next links returned by the confluence API should work.
What am I missing? Please help.
BR! /marcus
PS
Thanks to @nathanwaters for the tip on the thread on the pagination API changes, I have posted this same info and question in that thread; Upcoming changes to modernize search REST APIs
I did not see it before - I relied on the info atlassian posted on this change, this page: “Upcoming changes to Confluence Cloud REST APIs to modernize search”, https://developer.atlassian.com/cloud/confluence/change-notice-moderize-search-rest-apis/
Where they wrote: “To make sure your search code continues to work before, during, and after this change, use the prev and next links returned in the HTTP response instead of constructing them yourself.”