Overview
List endpoints support cursor-based pagination to efficiently retrieve large datasets.How It Works
Cursor-based pagination uses a cursor token to mark your position in the dataset. This allows you to fetch the next page of results without missing or duplicating items.Using Pagination
First Page
Make a request without a cursor to get the first page:Next Page
Use thenext_cursor from the previous response to fetch the next page:
Response Format
Paginated responses include ameta object with pagination information:
When
next_cursor is null, you’ve reached the last page.Parameters
| Parameter | Type | Default | Max | Description |
|---|---|---|---|---|
cursor | string | null | - | Cursor token from previous response |
limit | integer | 20 | 100 | Number of items per page |
Example Implementation
Best Practices
- Use appropriate page sizes: Choose a
limitthat balances performance and number of requests - Handle null cursors: Check if
next_cursorisnullto know when to stop - Store cursors: If you need to resume pagination, store the cursor token
- Respect rate limits: Don’t paginate too aggressively to avoid hitting rate limits

