Pagination

All list endpoints use cursor-based pagination. This is more reliable than offset-based pagination when data changes between requests.

Parameters

Parameter	Type	Default	Description
`limit`	integer	50	Number of items to return (max 100)
`cursor`	string	—	Opaque cursor from a previous response

{
  "data": [...],
  "next_cursor": "2026-04-01T12:00:00Z",
  "has_more": true
}

Field	Description
`data`	Array of results
`next_cursor`	Pass this as `cursor` to get the next page. `null` if no more results.
`has_more`	`true` if more results exist beyond this page

First page:

GET /api/v1/audit-log?limit=10

GET /api/v1/audit-log?limit=10&cursor=2026-04-01T12:00:00Z

Continue until has_more is false.

Cursors are opaque strings. Don’t parse or construct them — always use the value from next_cursor.
Results are ordered by created_at DESC (newest first) unless otherwise documented.
The maximum limit is 100. Values above 100 are clamped.