Skip to main content
Every list endpoint returns results in pages using cursor-based pagination. Cursors are object IDs, so paging stays stable even when objects are added or removed between requests.

Response Structure

List responses wrap results in a data array alongside a pagination object:
List response

Query Parameters

Paging Through Results

Omit starting_after to fetch the first page. For each subsequent page, pass the previous response’s next_cursor as starting_after. Stop when has_more is false, at which point next_cursor is null.
1

Fetch the first page

First page
2

Fetch the next page

Pass the previous response’s next_cursor as starting_after:
Next page