data array, a has_more flag, and a next_cursor value you pass on subsequent requests to fetch the next page.
Request parameters
| Parameter | Type | Default | Description |
|---|---|---|---|
limit | integer | 20 | Number of results per page. Min 1, max 100. |
cursor | string | Cursor from a previous response. Omit for the first page. |
Response format
Every list response has the same shape:Array of resource objects for the current page.
true if there are more results beyond this page. false on the last page.An opaque string to pass as the
cursor query parameter on the next request. null when there are no more pages.Unique identifier for the API request.
Fetching the next page
Passnext_cursor from the previous response as the cursor query parameter:
has_more is false.
Paginating through all results
Filtering and sorting
List endpoints may accept additional query parameters for filtering. Filters are applied server-side before pagination, so thelimit applies to filtered results.
Cursors are opaque
Cursor values are opaque strings. Do not parse, construct, or store them long-term. They encode internal position state and may change format between API versions.- Pass them exactly as received from the API.
- Do not reuse cursors across different endpoints or filter combinations.
- If a cursor becomes invalid, the API returns a
400error withcursor_invalid. Start from the first page.
