Skip to main content
All list endpoints return paginated results using cursor-based pagination. This approach provides stable, consistent paging even when new records are created between requests.

Query Parameters

Response Shape

Every list endpoint returns a data array and a _meta object:

Paging Forward

Pass the next cursor from the previous response to fetch the next page:
Continue until _meta.next is null.

Paging Backward

Pass the prev 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), with id 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 limit is 100. Requests above this value are clamped to 100.
  • The minimum limit is 1.
  • An invalid or expired cursor returns a 400 Bad Request error.
  • File listing (GET /files) uses GCS continuation tokens instead of database cursors, but the response shape and query parameters are identical.