Pagination
List endpoints accept two query parameters:
| Param | Type | Default | Max |
|---|---|---|---|
limit | number | 50 | 100 |
offset | number | 0 | - |
Two pagination shapes
Most endpoints return an offset-based shape:
"pagination": { "total": 142, "limit": 50, "offset": 0, "has_more": true }Two endpoints currently return a different shape (page, totalPages instead
of offset, has_more):
GET /events/:eventId/registrationsGET /super-events/:superEventId/registrations
"pagination": { "page": 1, "limit": 50, "total": 142, "totalPages": 3 }These endpoints also accept a page query parameter (1-indexed) instead of
offset. If you write a generic client, handle both shapes.
Iterating
For offset-based endpoints, increment offset by limit until
pagination.has_more is false. For the registrations endpoints, increment
page until page === totalPages.