How it works
Every list endpoint accepts two query parameters:| Parameter | Type | Description |
|---|---|---|
first | integer | Maximum number of items to return per page (default varies by endpoint) |
after | string | Opaque cursor from a previous response. Omit for the first page |
Response format
List responses include pagination metadata:| Field | Description |
|---|---|
items | Array of results for the current page |
has_next_page | true if there are more results |
end_cursor | Pass this as the after parameter to get the next page. null when has_next_page is false |
total | Total number of matching items (may be omitted by some endpoints for performance) |
Example: Paginating through sessions
First page
Next page
Use theend_cursor value from the previous response:
Collecting all results
Migrating from offset-based pagination
If you’re migrating from API v1 or v2, replaceoffset/limit with after/first:
