Pagination

List endpoints accept a limit parameter to control page size: default 50, max 100. Values above 100 are rejected with a 400.

Most list responses share a common envelope:

Field	Description
data	Array of results
cursor	Opaque token to fetch the next page, or null when no more pages
total	Total count of matching items

Which lists are actually paginated

Only the references list is cursor-paginated. The other list endpoints currently return all matching rows in a single response with cursor: null:

Endpoint	Behavior
GET /references	Cursor-paginated. cursor is non-null while more pages remain.
GET /folders	Returns all rows at once; cursor is always null.
GET /labels	Returns all rows at once; cursor is always null.
GET /files	Returns all rows at once; cursor is always null.
GET /folders/{folder_id}/folders	Returns a bare JSON array — no {data, total, cursor} envelope.

Example references response:

{
  "data": [...],
  "cursor": "eyJpZCI6MTIzFQ",
  "total": 250
}

To get the next page of references, pass the cursor back:

GET /references?cursor=eyJpZCI6MTIzfQ

When cursor comes back null, there are no further pages.