Skip to main content
APIs that use marker-based paging use the marker and limit query parameters to paginate through items in a collection. Marker-based pagination is often used in cases where the length of the total set of items is either changing frequently, or where the total length might not be known upfront.

​
Paging

To fetch the first page of entries in a collection the API needs to be called either without the marker parameter, or with the marker set to 0. The limit parameter is optional.
APIs that support both offset-based pagination and marker-based pagination require the usemarker query parameter to be set to true to ensure marker-based pagination is used.
To fetch the next page of entries the API needs to be called with an marker parameter that equals value of the next_marker value that was received in the API response.
The final page of items has been requested when the next next_marker value is null in the response object. At this point there are no more items to fetch.
With marker-based paging there is no way to determine the total number of entries in a collection except by fetching them all. Applications should not retain the next_marker value long-term as the internal implementation of the markers may change over time.

​
Marker & Limit

The following query parameters are used to paginate a collection.

​
Collections

When paginating collections, the API returns an object that contains the set of results as an array, as well as some information about the current page of results.

​
Example endpoints

Some endpoints that support marker-based pagination are:
Last modified on March 19, 2026