next_page value from a response as the page query parameter on the next request. Cursors remain stable even as data changes.
Request parameters
page, before_id, and after_id are mutually exclusive. Sending more than one cursor returns 400 invalid_request_error.Response structure
All list endpoints return the same pagination envelope:Field descriptions
Basic usage
Fetch the first page
Fetch the next page
Usenext_page from the previous response as page:
Compatibility cursors
Some endpoints also acceptbefore_id and after_id for ID-based cursor compatibility:
Full traversal example
The script below iterates through every Agent:limit behavior
Empty results
When there is no data or the end of the list has been reached:Notes
- Cursor stability —
pagecursors are opaque and should be passed back exactly as returned. - Sort order — records are returned in descending creation time by default (newest first).
- Compatibility cursors —
before_idandafter_idare retained for ID-based cursor compatibility. - Concurrent paging — paging is safe to perform concurrently from multiple clients.
Next steps
Overview
How Qoder Cloud Agents fits together.