Pagination

The cursor convention shared by list endpoints: limit, starting_after and has_more.

This is the convention of the list endpoints of the API. The current lists (GET /v1/agents and GET /v1/tasks) do not use it yet and keep their present format; the reference always shows the exact format of each endpoint.

Cursor pagination

Lists use a cursor, not page numbers, so results stay consistent while new items arrive. Items are returned newest first.

limit: number of items, from 1 to 100 (default 20).
starting_after: the id of the last item of the previous page. It must belong to the list you are reading (same organization, mode and filters): an unknown, deleted or foreign id answers 400 with invalid_cursor, never an empty page.
The response holds data (the items) and has_more (true when another page exists).

{
  "data": [ { "id": "item_3" }, { "id": "item_2" } ],
  "has_more": true
}

An out-of-range limit or a malformed cursor answers 400 with invalid_query.

Walk through every page

Request the first page without starting_after, then repeat with the id of the last item until has_more is false.

# First page
curl "https://infynia.quantylcore.com/api/v1/RESOURCE?limit=50" \
  -H "Authorization: Bearer $INFYNIA_API_KEY"

# Next page: id of the last item received
curl "https://infynia.quantylcore.com/api/v1/RESOURCE?limit=50&starting_after=item_2" \
  -H "Authorization: Bearer $INFYNIA_API_KEY"