To manage load on the API, various GET endpoints are paging. We generally do this in cases where the item type in question typically has a lot of items, as is the case (for example) with machines, nodes and people.

Page Request

For paging endpoints, request a page using the following HTTP request parameters:

Param Description Default Value
page Page index (0-indexed). 0
size Page size. Maximum value is 500. 100
sort Sort directives. See the examples below for the formats. None. If sort isn't specified, the results aren't sorted.


Single sort key, default sort direction (asc):


Single sort key, descending sort:


Multiple sort keys, same sort direction:


Multiple sort keys, different sort directions:


Page Response

The API communicates page metadata in the HTTP response headers. The API supports the standard Link header. We also provide a set of extension headers to make it easier for clients to get at the URIs without having to parse Link.

Header Description
Link Standard HTTP header for presenting relevant links.
X-Pagination-First URI for the first page
X-Pagination-Prev URI for the previous page
X-Pagination-Next URI for the next page
X-Pagination-Last URI for the last page
X-Pagination-TotalElements Total number of elements in the result set
X-Pagination-TotalPages Total number of pages in the result set




Link: <>;rel="self",<>;rel="first",<>;rel="prev",<>;rel="next",<>;rel="last"
X-Pagination-TotalElements: 1904
X-Pagination-TotalPages: 39