Skip to main content
The v3 API uses offset-based pagination. Each paginated endpoint accepts limit and offset parameters. limit controls how many results to return per request, and offset skips a number of rows from the beginning of the result set. To retrieve the next page, increment offset by the value of limit. The following endpoints support pagination: All other v3 endpoints return single objects or fixed results and do not support pagination.

Parameters

These parameters are shared across all paginated endpoints.

Pagination example

This example uses the transactions endpoint, but the same limit and offset pattern applies to all paginated endpoints.
1

Fetch the first page

Send a request with account and limit. offset defaults to 0 for the first page.
Response (abbreviated):
Three transactions returned, sorted by logical time in descending order (newest first).
2

Fetch the next page

Set offset=3 to skip the first 3 results and get the next batch.
Response (abbreviated):
No overlap with the previous page. Offset pagination does not produce duplicates.
3

Repeat until the last page

Continue incrementing offset by the limit value on each request (offset=6, offset=9, …). When the response returns fewer transactions than the limit, all results have been retrieved.
Output:

Sorting options

Sortable endpoints accept a sort parameter with two values:
  • desc (default): newest results first, sorted by logical time (or UTC timestamp for blocks).
  • asc: oldest results first.
Response (abbreviated):
With sort=asc, the earliest transactions are returned first, starting from 2023-07 for this account.