Skip to main content
Every Main API list endpoint uses cursor pagination. Cursors are stable across inserts and deletes, so you never miss or duplicate a record while paging.
Pagination applies to the Main API only. The Extended API exposes utility endpoints (validation, lookups, dispatch) and has no list endpoints.

Request parameters

Response shape

has_more is derivable: it’s nextCursor !== null.

Response headers

For convenience, list endpoints also emit:

Walking a list

Sort

Pass sort as a single field name. Prefix with - for descending order:
Endpoints document their valid sort fields. Sorting on a non-indexed field returns 400 parameter_invalid_format.

Filtering

Use simple ?key=value filters where supported. The fielded query language (AIP-160 syntax) is on the roadmap.

Limits in practice

  • Use limit=100 for bulk processing. Fewer round-trips, predictable headers.
  • Use limit=25 (the default) for interactive UIs.
  • Going above 100 returns 400 parameter_invalid_format.

Next steps

Rate limits

Stay under per-IP rate limits while paging.

Errors

Status codes and the code catalogue.