Skip to main content
List endpoints are cursor-paginated. A page comes back as { data, has_more, next_cursor }; pass next_cursor back as cursor to fetch the following page.
array
required
The rows for this page.
boolean
required
Whether another page exists. Prefer this over checking whether data is full.
string
Opaque. Pass it back as cursor. Absent on the final page.

Auto-paging

The TypeScript and Python SDKs hide the cursor loop entirely — iterate the list and it fetches pages as you go.
Go pagination is currently single-page. PaginatedResponse.Cursor is deserialized from cursor, but the API sends the next cursor as next_cursor, so the field never populates and a cursor loop stops after the first page. Read page.HasMore and raise Limit until this is fixed.

Choosing a page size

limit defaults to 25 and caps at 100. Larger pages mean fewer round trips but a slower first byte. For bulk export, 100 with auto-paging is usually right; for an interactive list, 25 keeps the first page fast.