Pagination
Dockt collection endpoints use cursor pagination.
Request a page
Section titled “Request a page”Use limit to request between 1 and 100 resources. The default is 20:
GET /v1/assessments?limit=50Collection responses include:
{ "object": "list", "data": [], "has_more": true, "next_cursor": "OPAQUE_CURSOR"}Request the next page
Section titled “Request the next page”When has_more is true, send the returned next_cursor unchanged:
GET /v1/assessments?limit=50&cursor=OPAQUE_CURSORStop when has_more is false or next_cursor is null.
Cursor rules
Section titled “Cursor rules”- Treat the cursor as an opaque string.
- Don’t parse, modify, or construct cursors.
- Keep the same filters and page size while walking one collection view.
- Start a new pagination sequence when filters change.
- Handle an invalid or expired cursor as
400 Bad Requestand restart from the first page when appropriate. - Don’t use a cursor from one endpoint on another endpoint.
Collection-specific filters appear in the API reference.