Radar API / Developer guide
Pagination & consistency
Use signed cursors with unchanged filters and a strict page budget.
Read as MarkdownContinue a bounded query
Read pagination.next_cursor and pass it back unchanged with the same filters. Stop when it is null, pagination.has_more is false, or your page/result budget is reached. Each request needs a new request ID. Preview pagination is unavailable.
Consistency
Cursors bind the query filters and keyset position. They do not freeze inventory into a transaction snapshot. Records may change or disappear between requests. Deduplicate returned canonical IDs in your own bounded workflow.
Invalidation
The current implementation does not encode a time-to-live into cursors. Do not rely on indefinite validity: signing-key rotation or incompatible query changes can invalidate them. On malformed_cursor, discard it and restart a small query. There is no offset pagination contract.