Skip Main Navigation
Page Content

Paginated Responses

All API endpoints which return multiple objects will return paginated responses; as well as the list of objects (which will usually be under a key like events or attendees, depending on the endpoint) there will also be a pagination key:

{
    "pagination": {
        "object_count": 13,
        "page_number": 2,
        "page_size": 50,
        "page_count": 2
    },
    "events": [
        ...
    ]
}

This pagination key gives you information about the number of pages in the result, and how many objects are returned:

  • page_number: The current page number (starts at 1)
  • page_size: The number of objects on each page (roughly)
  • object_count: The total number of objects across all pages (optional)
  • page_count: The total number of pages (starting at 1) (optional)

You can specify the page number you would like to request using the page parameter. However, page sizes are fixed, usually around 50 objects per page, but it may be smaller or larger depending on the particular endpoint (the sizes are tuned to improve API response speed and cacheability).

In addition, you’re not guaranteed to get back the given number of items per page; you may get more or less depending on pagination backend optimizations. It should be treated as a rough guide.

Note that while we guarantee stable ordering of objects in paginated resources, the objects being returned may change between requests (e.g. the orders endpoint for a fast-selling event; between requesting page 1 and page 2, more items may have appeared on or been removed from page 1).

These endpoints will usually have an alternative way of querying without missing objects, however, often based off of modified times. See the individual endpoint pages for details.

Also note that on some endpoints, you won’t get back object_count and page_count, and you’re expected to just keep incrementing the page number until you get the BAD_PAGE error or you have enough data. These endpoints typically have a very large number of results (for example, the endpoint that lists every event on Eventbrite), and calculating the exact count would take too long.