Store and contact search endpoints use cursor pagination.
Request the first page with limit, then pass next_cursor to fetch the next page.
Rules
- Cursor tokens are opaque. Do not parse them or build your own.
- Keep the request body stable between pages.
- If filters change, discard the previous cursor and start a new search.
- An empty
data array with no next_cursor means the result set is exhausted.
- Cursors are tied to the original API key and query shape.
Changing filters while reusing a cursor returns an invalid cursor error.
