Skip to main content
List endpoints paginate in one of the following ways. Exact field names are on each operation in the REST reference.

​
Page number and size

Many node and indexer list routes accept pageNumber (zero-based) and pageSize as query parameters. Defaults are typically pageNumber=0 and pageSize=2000; the indexer caps several routes at 2000.
  1. Start at pageNumber=0 with a reasonable pageSize.
  2. If the response is empty or shorter than pageSize, you have the last page.
  3. Otherwise request pageNumber + 1.

​
Time range and limit

Candles, order history, and the default trades mode use startTime / endTime (milliseconds) and limit.
  • endTime defaults to now; startTime defaults to 24 hours before endTime.
  • limit defaults to 500 (max 1000 for these routes).
Portfolio and vault history use from / to / interval. from=0 and to=0 mean all available history through the latest snapshot.

​
Cursor (trades)

GET /indexer/trades also supports count (1–100) with an optional cursor for latest-fills pagination. count cannot be combined with startTime, endTime, or limit. The response may include nextCursor for the next page.

​
Client tips

  • Cap page size and time range to avoid timeouts and large payloads.
  • Do not assume global ordering unless the endpoint documentation states a sort order.