Offset pagination
Most list endpoints use offset pagination withpage and size parameters.
Request
| Parameter | Type | Description | Default |
|---|---|---|---|
page | integer | Page number (0-based) | 0 |
size | integer | Items per page (1–200) | 10 or 20 (varies by endpoint) |
sort | string | Sort field | varies |
sortOrder | string | ASC or DESC | ASC |
Response
Offset endpoints return one of two response shapes: With total count (PageResult):
TableValueResult):
Iterating through pages
Cursor pagination
Time-series and append-only data uses cursor pagination for consistent results.Request
| Parameter | Type | Description | Default |
|---|---|---|---|
cursor | string | Opaque cursor from previous response | (start from beginning) |
limit | integer | Items per page | 50 (varies: 1–200) |
Response
Iterating with cursors
Endpoints using cursor pagination
- Check results (
/api/v1/monitors/{id}/check-results) - Service catalog (
/api/v1/services) - Service poll results
- Webhook deliveries
Single value responses
Some endpoints return a single item wrapped in adata field:
Sorting
For offset-paginated endpoints that acceptsort, pass the field name. Common sortable fields:
createdAt— creation timestamp (most common default)name— alphabeticalupdatedAt— last modifiedstatus— resource status
sort=name,asc&sort=createdAt,desc.