Skip to main content
All list endpoints in the Organization and Enterprise APIs use cursor-based pagination. This provides consistent, efficient pagination regardless of the size of the result set.

How it works

Every list endpoint accepts two query parameters:

Response format

List responses include pagination metadata:

Example: Paginating through sessions

First page

Next page

Use the end_cursor value from the previous response:

Collecting all results

Migrating from offset-based pagination

If you’re migrating from API v1 or v2, replace offset/limit with after/first:
Cursor-based pagination is more reliable than offset-based pagination because it isn’t affected by items being added or removed between pages.