Pagination in the API is handled via the Link header standard:
$ curl -i https://sentry.io/api/0/projects/1/groups/
HTTP/1.0 200 OK Date: Sat, 14 Feb 2015 18:47:20 GMT Content-Type: application/json Content-Language: en Allow: GET, HEAD, OPTIONS Link: <https://sentry.io/api/0/projects/1/groups/?&cursor=1420837590:0:1>; rel="previous"; results="false", <https://sentry.io/api/0/projects/1/groups/?&cursor=1420837533:0:0>; rel="next"; results="true"
In this example we have both a ‘previous’ link and a ‘next’ link. The meaning of these links depends on the input query, but in our above example the ‘previous’ page would be page index -1, and the next page would be page index 1.
When supported, cursors will always be returned for both a previous and a next page, even if there are no results on these pages. This allows you to make a query against the API for yet-undiscovered results. An example where this would be used is when you’re implementing polling behavior and you want to see if there is any new data. To help understand if you actually need to paginate we return a