Skip to main content
All list endpoints use cursor-based pagination. This is more efficient than offset pagination for large datasets and is stable under concurrent writes.

How it works

Every list response includes a pagination object:
  • has_more: true means there are more results to fetch
  • next_cursor is an opaque string — pass it as the cursor query parameter to get the next page
  • When has_more is false, you have reached the last page and next_cursor is null

Fetching all pages

Parameters

Tips

  • Use from/to to scope your query. Paginating across years of tick data without a time range will be slow. Always specify from and to for large exports.
  • Cursors are not permanent. Don’t store cursors for later use — they encode a position within a specific query and may expire.