Skip to main content
All list endpoints use cursor-based pagination. This is more reliable than offset-based pagination: insertions and deletions don’t cause skipped or duplicated records.

Request parameters

Response format

Every list endpoint returns the same pagination structure:

Paginating through all results

Filtering and sorting

List endpoints support filters via query parameters. Filters are combined with pagination:
Available filters vary per endpoint — check the specific resource documentation for details.
Cursors are opaque strings. Don’t try to decode, modify, or construct them manually. Always use the next_cursor value returned by the API.

Best practices

  • Use the largest limit you need. Fewer requests = fewer rate limit tokens consumed. Use limit=100 for bulk operations.
  • Stop when has_more is false. Don’t make an extra request — the API tells you when you’ve reached the end.
  • Use total_count for progress. Display progress bars or “showing X of Y” indicators using total_count.