Pagination

How Platform API list endpoints paginate - continuation-token pagination for resource lists and limit/offset for analytics and audit endpoints.

The Platform API uses two pagination styles, and knowing which one an endpoint uses tells you how to request the next page. Most resource list endpoints (agents, skills, services, triggers, the metric list, and similar) use continuation-token pagination. Other endpoint groups - audit logs, intake links, conversations, calls, FHIR views, world model, population health, and similar query-style endpoints - use limit/offset pagination instead.

Continuation-Token Pagination (Default)

Resource list endpoints return items, has_more, and continuation_token, with an optional total:

{
  "items": [...],
  "total": 142,
  "has_more": true,
  "continuation_token": 20
}

Parameter	Default	Range	Description
limit	10	1-100	Items per page. Most resource lists default to 10 with a maximum of 100; some (such as integrations and intake lists) default to 50 with a maximum of 200.
continuation_token	-	-	Cursor for the next page. Returned in the response; pass it back unchanged. On many endpoints it is an integer offset, but treat it as opaque.

The total field is optional and only populated for endpoints that opt in, so it is not returned on every paginated response. When has_more is true, pass the returned continuation_token back to fetch the next page.

Limit/Offset Pagination

The endpoint groups tabled below accept limit and offset query parameters directly.

Parameter	Type	Default	Description
limit	integer	Varies by endpoint	Maximum number of items to return. Must be >= 1. Upper bound varies by endpoint.
offset	integer	0	Number of items to skip before returning results. Must be >= 0.

Both parameters are optional. Omitting them returns the endpoint's default result set.

Example

# First page of 25 results
curl -H "Authorization: Bearer $API_KEY" \
  "https://platform.api-us.concurrence.com/v1/$WORKSPACE_ID/audit?limit=25&offset=0"

# Second page
curl -H "Authorization: Bearer $API_KEY" \
  "https://platform.api-us.concurrence.com/v1/$WORKSPACE_ID/audit?limit=25&offset=25"

Supported Endpoints

Representative endpoint groups and their limits (not an exhaustive list - each endpoint's reference documentation states its own default and maximum). Rows labeled "population health" are the endpoints under the /v1/{workspace_id}/m42/ path prefix, which serve the population health analytics surface.

Endpoint Group	Default Limit	Max Limit
Audit exports (limit only, no offset)	50	200
Entity duplicates	100	500
Intake links	100	500
Intake uploads (per link)	200	500
Voice judge results	20	100
Prompt logs	20	200
Entity enrichment values	200	500
Enrichment keys	200	500
Population health (m42) district metrics	50	500
Population health (m42) anomaly alerts	50	500
Population health (m42) forecast fan	1000	5000
Population health (m42) positive signals	50	200
Population health (m42) ranked anomalies	50	500
Population health (m42) cluster summary	50	500
Population health (m42) cluster forecast	1000	5000
Population health (m42) model registry	50	500
Population health (m42) stratified fits	50	500
Population health (m42) patient topology	10000	50000
Population health (m42) patient labs	500	2000

Validation

Requests with limit or offset values outside the allowed range receive a 422 Unprocessable Entity response. The limit must be at least 1 and at most the endpoint's maximum. The offset must be non-negative.

Notes

• Result ordering is preserved as documented for each endpoint. Pagination slices the ordered result set.
• If offset exceeds the total number of available results, an empty list is returned.
• Total count headers are not included in responses. Most limit/offset endpoints signal the end of a result set implicitly: check whether the number of returned items is less than the requested limit.
• Some endpoints return explicit peek-ahead pagination fields instead. Prompt Logs responses include has_more and next_offset (with a 10,000 offset cap); pass next_offset back as offset for the next page.