Pagination and queries
Page through lists without teaching the wrong arithmetic.
List endpoints take page and page_size. The response meta tells you how to continue:
| Field | Meaning |
|---|---|
page |
Current page, 1-based |
page_size |
Page size used for this response |
total_count |
Total matching rows |
total_pages |
ceil(total_count / page_size), at least 1 |
has_next |
page < total_pages |
has_prev |
page > 1 |
page_size is bounded. The API client prefills the example values published in the spec; those values are inside the documented range, so a test request does not 422.
Do not send a filter the route does not declare. Unknown query names are ignored or rejected depending on the endpoint — use the API Reference.
Cursor-style tokens are not used. If has_next is true, request page + 1 with the same filters and page_size.
