Platform / Platform

List endpoint pagination

List endpoints return collections of resources. Pagination behavior varies by surface.

01 REST API list endpoints

details

Keyed array responses

Collection responses use a resource key such as {"messages": [...]} or {"eval_runs": [...]}. Workspace scoping still comes from authentication; pagination parameters never widen tenant scope.

02 Bounded limit/offset endpoints

reference

Endpoint	Parameters	Response metadata
GET /api/v1/messages	limit: 1-100 (default 50); offset: 0-100000	messages and count
GET /api/v1/tasks	limit: 0-100 (default 50); offset: 0-10000	tasks, count, and pagination
GET /api/v1/operator/eval_runs	limit: 0-100 (default 50); offset: 0-10000	eval_runs and pagination
GET /api/v1/operator/agent_commands	limit: 1-100 (default 25)	agent_commands

03 SCIM 2.0 pagination

details

Parameters

startIndex (1-based, default 1), count (max results per page, default 100), filter (SCIM filter expression e.g. userName eq "user@example.com").

Response envelope

Returns schemas, totalResults, startIndex, itemsPerPage, and Resources array following the SCIM 2.0 ListResponse standard.

04 SCIM list response example

example

json

{
  "schemas": ["urn:ietf:params:scim:api:messages:2.0:ListResponse"],
  "totalResults": 42,
  "startIndex": 1,
  "itemsPerPage": 100,
  "Resources": [
    {
      "schemas": ["urn:ietf:params:scim:schemas:core:2.0:User"],
      "id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
      "userName": "user@example.com",
      "active": true
    }
  ]
}

Related docs