Pagination
List endpoints use cursor-based pagination. Parameter names, defaults, and response schemas are documented per endpoint in the API reference.
How it works
- Make the initial request without a
cursor. - Process the
dataarray in the response. - If
nextCursoris notnull, request the next page with that value as thecursorparameter — keep the samelimitand filters. - Stop when
nextCursorisnull.
Use Try it out in the API reference on any list endpoint to see the live request/response shape.
Filter binding
Cursors are bound to the filter parameters used when they were issued, and to your API key's brand. If you change filters between pages, or use a cursor with a different key's brand, the cursor becomes invalid and the API returns 422. When that happens, restart pagination from the first page with your new filters.
A cursor can also be invalidated by an API release, even if you did not change anything. Treat a 422 on a cursor the same way: restart pagination from the first page.
Cursor rules
- Opaque — do not parse, construct, or modify cursor values.
- Signed — tampered tokens are rejected.
- Stable within a sequence — list ordering is consistent while you paginate, but do not assume a particular sort order unless an endpoint documents one.
See Errors for retry guidance when a cursor is rejected.