Query Parameters
| Parameter | Type | Default | Description |
|---|---|---|---|
limit | integer | 20 | Number of items per page (1—100) |
cursor | string | — | Opaque cursor from a previous response |
Response Shape
Every list endpoint returns adata array and a _meta object:
| Field | Description |
|---|---|
_meta.next | Cursor pointing to the next page. null when there are no more results. |
_meta.prev | Cursor pointing to the previous page. null on the first page. |
_meta.limit | The limit that was applied to this request. |
Paging Forward
Pass thenext cursor from the previous response to fetch the next page:
_meta.next is null.
Paging Backward
Pass theprev cursor to go back one page. This is useful for building “Previous / Next” navigation in a UI.
Sort Order
Results are sorted by creation date descending (newest first), withid as a tiebreaker. This order is fixed and cannot be changed via query parameters.
Cursor Format
Cursors are opaque strings — do not parse, construct, or store them long-term. They encode an internal position and may change format between API versions. Always use the cursor values returned in_meta.
Example: Fetching All Projects
Notes
- The maximum
limitis 100. Requests above this value are clamped to 100. - The minimum
limitis 1. - An invalid or expired cursor returns a
400 Bad Requesterror. - File listing (
GET /files) uses GCS continuation tokens instead of database cursors, but the response shape and query parameters are identical.