Documentation details several pagination styles. Which endpoint returns a pagination exclusively for pages? For example:
optionGroup = ['segment', 'response', 'collection', 'entry', 'entry_bundle', 'detail_item', 'profile']
i think its the /pages endpoint that handles pagination exclusively for pages. docs can be confusing tho, but thats what i’ve seen in practice.
Based on my experience, the pagination dedicated to pages often appears when the endpoint is explicitly dealing with information and metadata unique to page objects rather than generic content blocks. In practice, when performing queries that filter out non-page entities, the API defaults to a pagination schema that is optimized for page retrieval. This behavior likely stems from the design that separates how pages are handled from other types of content, ensuring efficient management of page data and navigation through extensive lists.
After some hands-on work with the Notion API, I’ve come to notice that pagination exclusively for pages manifests particularly when requests are clearly targeting page objects. In my tests, retrieving data through the /pages endpoint or when specifying queries that only filter page attributes led to a distinct pagination format. This behavior suggests the API is designed to optimize data retrieval for pages separately from other content types. It seems that isolating pages in your request triggers a device where pagination is tailored specifically for page-based metadata and management.