API Reference
Pagination
List endpoints use cursor-based pagination for stable navigation, even as data changes between requests.
Paginated responses include:
dataThe list of returned items.hasMoreWhether more items are available.cursorOpaque pointer to the next page, present only when hasMore is true. Pass it back as after.Control each request with these query parameters:
limitNumber of items to return per page (1–100, default 50).afterCursor from a previous response's cursor field; returns the next page.Pagination is forward-only. Read the cursor from each response and pass it as after to get the next page — treat cursors as opaque; don't construct or parse them.
Response format
Fetching every page
Supported endpoints
Best practices
- Always check
hasMorebefore requesting another page - Choose a
limitthat balances performance and usability — smaller pages for real-time UIs, larger for bulk processing - Be mindful of rate limits when paginating through large datasets
Error handling
Pagination requests may return the following validation error:
| Error | Description |
|---|---|
VALIDATION_ERROR | The limit is out of range (must be 1–100). |