Skip to main content
List endpoints return results one page at a time using cursor-based pagination. Each response includes a data array for the current page, a has_next boolean, and a cursor string to fetch the next page. Cursor pagination is stable within a single pass: inserting or deleting records while you page will not cause items to be skipped or duplicated.

Query parameters

All paginated endpoints accept these parameters: A limit that is not a whole number between 1 and 100 is rejected with a 400 error.

Response structure

cursor is null when this is the last page. Pass it as the cursor query parameter on the next request to fetch the following page.

Fetching all pages

To retrieve every item, keep requesting until has_next is false:

Keeping a local copy in sync

Do not save a cursor and reuse it on a later run. Cursors page from newest to oldest, so resuming from a stored cursor returns records older than your bookmark and never the new ones that arrived above it. There is also no cursor to save at the end of a pass: cursor is null on the last page.