How it works
- Make your first request (no cursor):
- Check
has_moreandnext_cursorin the response (the list itself is under a resource key:signalsfor/v1/signals,entitiesfor/v1/entities):
- Pass
next_cursoras thecursorparameter for the next page:
- Repeat until
has_moreisfalse.
Parameters
Paginated endpoints
GET /v1/signals: signals listGET /v1/entities: entities list
Why cursor-based?
Cursor pagination is more efficient and consistent than offset-based pagination:- No skipped/duplicated results when data changes between pages
- Consistent performance regardless of page depth (no
OFFSET Nscan) - Opaque cursors: the format may change without breaking clients