Pagination
Klozeo uses cursor-based (keyset) pagination — not offset-based. This prevents duplicate or skipped results when data changes between pages.
Parameters
Section titled “Parameters”| Parameter | Default | Max | Description |
|---|---|---|---|
limit | 50 | 1000 | Results per page |
cursor | — | — | Opaque token from previous response |
Response fields
Section titled “Response fields”{ "leads": [...], "next_cursor": "eyJpZCI6ImNsXzAxMjM...", "has_more": true, "count": 50}| Field | Description |
|---|---|
next_cursor | Pass as cursor in next request. Null if no more pages. |
has_more | true if there are more results |
count | Number of results in this page |
# First pagecurl "https://api.klozeo.com/api/v1/leads?limit=50" \ -H "X-API-Key: sk_live_your_key"
# Next pagecurl "https://api.klozeo.com/api/v1/leads?limit=50&cursor=eyJpZCI6ImNsXzAxMjM..." \ -H "X-API-Key: sk_live_your_key"Important
Section titled “Important”- The cursor is opaque — do not parse or construct it manually.
- Cursors encode the current sort position. Changing
sort_byorsort_orderinvalidates the cursor. - Filters are preserved across pages — pass the same
filterparams with each request. - For complete dataset export without pagination, use the Export endpoint instead.