Which Confluence REST API pagination strategy best avoids duplicates in large datasets?
When pulling a full list of pages from Confluence via the REST API, the endpoint caps each request to 1,000 results and requires an offset via the start parameter. The goal is to enumerate every page reliably, even when the dataset exceeds the hard limit. Because the API is offset‑based, inserting or deleting pages between paginated calls can cause the same
confluence