Skip to main content
All Tilta list endpoints use offset-based pagination, which lets you retrieve large result sets in manageable chunks by specifying a starting position and a maximum page size. Every paginated response includes a total field that tells you how many records exist in total, so you always know when you have retrieved everything.

Query parameters

Pass the following query parameters on any list endpoint to control pagination:

How to paginate

1

Request the first page

Start with offset=0 and your desired limit. The response body will include the first batch of results and a total field indicating how many records exist across all pages.
2

Inspect the response

The response contains the result array and pagination metadata:
In this example, total is 347, meaning there are three more pages to fetch after this one.
3

Request the next page

Calculate the next offset by adding the previous limit to the previous offset:
For the second page:
4

Detect the last page

You have retrieved all records when the next offset would exceed the total:
For the example above with total=347 and limit=100:

Complete pagination loop

The example below shows a full pagination loop in Python that collects every order into a single list:
Request the largest limit your use case allows to minimise the number of round trips. For bulk exports or background sync jobs, a limit of 100 is a good starting point. For real-time UI pagination, a smaller limit (e.g. 20) typically provides a better user experience.
Offset-based pagination reflects the state of the result set at query time. If records are created or deleted between page requests, you may see slight inconsistencies (a record appearing on two pages, or being skipped). For critical reconciliation tasks, compare against the total field and re-fetch if the count changes unexpectedly.