Skip to main content
All list endpoints in the Clarky API return paginated results. Pagination is page-based — you ask for a specific page and a page size, and the response tells you how many pages there are in total.

Query parameters

integer
default:"1"
The 1-indexed page number to fetch.
integer
default:"25"
Number of items per page. Maximum is 100. Requests above the maximum return validation_error.

Response shape

Every list endpoint wraps results in data (the items for the current page) and pagination (metadata about the pagination state).
integer
The current page number (1-indexed).
integer
Number of items returned per page.
integer
Total number of items across every page.
integer
Total number of pages. total_pages is Math.ceil(total / page_size).

Examples

Fetch the first page

Fetch a larger page

Iterate every page

For large backfills, prefer page_size=100 to minimize round-trips, and respect the rate limits by backing off when you see 429 responses.

Endpoints that don’t paginate

A small number of endpoints return collections without pagination because the result set is bounded — for example, stages within a pipeline. These return { "data": [...] } with no pagination object. The shape is documented per-endpoint.

Single-resource responses

For endpoints that return a single resource (e.g. GET /contacts/{id}), the response is just { "data": { ... } } — no pagination object.