Query parameters
| Parameter | Type | Default | Notes |
|---|---|---|---|
limit | integer | 10 | Maximum number of items to return. Upper bound is typically 100. |
skip | integer | 0 | Number of items to skip before returning the page. |
search | string | — | Case-insensitive substring match on the entity’s primary text fields. |
sort | string | endpoint-specific | A sort directive (e.g. -createdAt for descending). Not every list endpoint supports arbitrary sort keys — check the endpoint’s schema. |
fromDate / toDate on most endpoints. A few older endpoints use startDate / endDate — check the endpoint page for the canonical parameter names.
Response shape
Most paginated endpoints return an envelope:| Field | Description |
|---|---|
totalCount | Total number of matching entities, ignoring limit and skip. Use this to drive pagination UI. |
edges | Array of entities for the current page. Array length is at most limit. |
A handful of older list endpoints return
{ items } or a bare array instead of { totalCount, edges }. The endpoint page will reflect the actual schema — always prefer the per-endpoint schema over assumptions.Requesting a page
Paginating through every page
Common errors
| Status | Cause | Fix |
|---|---|---|
400 BAD_REQUEST — limit must be a positive integer | Non-integer or negative limit | Use a positive integer, capped at 100 |
400 BAD_REQUEST — skip must be non-negative | Negative skip | Use 0 or a positive integer |
400 BAD_REQUEST — Invalid sort key | Endpoint doesn’t support the requested sort | Check the endpoint’s schema for supported sort values |
Related
Errors
Error envelope and common status codes.
Internationalization
Translating response bodies with
x-language.
