Skip to main content
List endpoints in the Qoder Cloud Agents API use cursor-based pagination. Use the 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

Use next_page from the previous response as page:

Compatibility cursors

Some endpoints also accept before_id and after_id for ID-based cursor compatibility:

Full traversal example

The script below iterates through every Agent:

limit behavior

Passing limit > 100 returns 400. Use limit=100 and page to page through larger result sets.

Empty results

When there is no data or the end of the list has been reached:

Notes

  1. Cursor stabilitypage cursors are opaque and should be passed back exactly as returned.
  2. Sort order — records are returned in descending creation time by default (newest first).
  3. Compatibility cursorsbefore_id and after_id are retained for ID-based cursor compatibility.
  4. Concurrent paging — paging is safe to perform concurrently from multiple clients.

Next steps

Overview

How Qoder Cloud Agents fits together.