Pagination

List endpoints use cursor-based pagination. Parameter names, defaults, and response schemas are documented per endpoint in the API reference.

How it works

  1. Make the initial request without a cursor.
  2. Process the data array in the response.
  3. If nextCursor is not null, request the next page with that value as the cursor parameter — keep the same limit and filters.
  4. Stop when nextCursor is null.

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

See Errors for retry guidance when a cursor is rejected.