Skip to main content
List endpoints page by offset. You choose how many records to get with size and how many to skip with from, and the RecordCount response header tells you how many records match in total.

Endpoint

Offset paging applies to these list endpoints:

Parameters

On the contact summary endpoints, send these as query parameters. On CCP logs, put them inside the criteria JSON object.

Response

Each page is a plain JSON array, with no wrapper object and no next-page token. Two things tell you where you are: Results are sorted newest first unless you set a sort. Contacts that arrive while you page push later records onto the next page, so you can see a record twice. Set toTime to a fixed past timestamp rather than now so every page sees the same set. OpenSearch caps how deep offset paging can go. A request where from plus size passes its result window fails with 422. To read further back, move the time window instead of raising from.

Example

A loop that fetches every contact in a 48-hour window:

Errors

Error bodies are plain text. See Errors for errors every endpoint can return.