How Pagination Works
Control the size and position of your result window using two query parameters:| Parameter | Type | Default | Max | Description |
|---|---|---|---|---|
limit | integer | 20 | 100 | Number of records to return per page |
offset | integer | 0 | — | Number of records to skip before returning results |
Pagination Response
Every list endpoint wraps its results in a consistent envelope with apagination object alongside the data array:
pagination fields tell you everything you need to know:
| Field | Type | Description |
|---|---|---|
total | integer | Total number of matching records across all pages |
limit | integer | The limit value used for this response |
offset | integer | The offset value used for this response |
has_more | boolean | true if more records exist beyond this page |
has_more as your loop condition — when it’s false, you’ve reached the last page.
Fetching All Pages
To collect every record, loop through pages untilhas_more is false, incrementing offset by limit on each iteration.
Best Practices
Follow these guidelines to paginate efficiently and avoid unnecessary load on your integration:Use reasonable page sizes
Aim for 20–50 records per page. This balances network overhead against the cost of many round trips. Only increase toward 100 if you’re doing batch processing offline.
Don't fetch everything unless you need to
If you only need the first few matching records, stop after the first page. Fetching all pages when you only display 10 results wastes bandwidth and counts against your rate limit.
Use filters to reduce result sets
Narrow your query with available filter parameters before paginating. Fewer total records means fewer pages and faster processing.
Respect rate limits between pages
When iterating many pages programmatically, add a small delay between requests or monitor your
X-RateLimit-Remaining header to avoid hitting the limit mid-loop.The
total count reflects the number of records matching your query at the
time of the first request. If records are created or deleted while you
paginate, your final count may differ slightly. For consistency-sensitive
workflows, consider processing data in a single session without long pauses
between pages.