Skip to main content
All list endpoints follow the same conventions for pagination, sorting, and filtering. The sort fields and filters each endpoint supports are listed in its API reference.

​
Pagination

List endpoints use cursor-based pagination. Each response contains a page of up to 100 results in data and a link to the next page in links.next:
To get the next page, request the URL in links.next as it is. It keeps your sorting and filters. When links.next is null, you have reached the last page.

​
Sorting

Use the sort query parameter to sort results by a field. Results are sorted in ascending order. Prefix the field with - to sort in descending order:
If you omit sort, the endpoint’s default sort order applies. An unsupported sort field returns 400 Bad Request. Results with the same value in the sort field always appear in the same order, so pagination doesn’t skip or repeat results.

​
Filtering

Filters use query parameters in the form filter[name]=value:
  • If you combine filters, results must match all of them.
  • An unsupported filter or an invalid value returns 400 Bad Request.
  • Filters ending in _since, such as filter[created_since], match results at or after the given timestamp. Timestamps must use the format YYYY-MM-DDTHH:MM:SSZ in UTC.
For example, to get all parcels created through the API since October 1, 2026:
With curl, add -g (--globoff) to URLs with filters. Otherwise, curl interprets the brackets as a URL pattern and doesn’t send the request. Other HTTP clients send brackets as they are or encode them automatically. The API accepts both.