Cursor-based pagination scheme used by all list endpoints in the Qoder Cloud Agents API.
List endpoints in the Qoder Cloud Agents API use cursor-based pagination. Use before_id and after_id to navigate the data window. Cursors remain stable even as data changes.
before_id and after_id are mutually exclusive. Sending both returns 400 invalid_request_error.
Some resources (Files, Skills, Vaults) use after/before as parameter names in their list endpoints, which are equivalent to after_id/before_id defined on this page — the server accepts both.
Use last_id from the previous response as after_id:
# Get the 10 records after agent_def456curl -s "https://api.qoder.com/api/v1/cloud/agents?limit=10&after_id=agent_def456" \ -H "Authorization: Bearer $QODER_PAT"
# Get the 10 records before agent_abc123curl -s "https://api.qoder.com/api/v1/cloud/agents?limit=10&before_id=agent_abc123" \ -H "Authorization: Bearer $QODER_PAT"
Silently capped at 100 (HTTP 200, no error). has_more reflects whether additional records remain
Passing limit > 100 does not return 400 — the API silently truncates the page to 100 records. Code that assumes limit=500 returns 500 records will only get the first 100 with no error signal. Use after_id to page through the rest.
# Fetch a single record to check whether data existscurl -s "https://api.qoder.com/api/v1/cloud/agents?limit=1" \ -H "Authorization: Bearer $QODER_PAT"