Introduction to the Qoder Cloud Agents API, gateway URL, request limits, and required headers.
The Qoder Cloud Agents API provides full management capabilities for cloud-hosted AI Agents, covering Agent creation, environment configuration, session management, event streaming, and more. All endpoints follow REST conventions and use JSON for requests and responses.
The API is currently at version
Every API request must include the authentication header; Content-Type is recommended but not mandatory — the server can auto-detect:
Successful response:
The API application layer currently has no active rate limiting. The gateway layer has global burst traffic suppression and DDoS protection, which may return 429 or 503 when triggered. Clients should implement exponential backoff retry for 5xx/429 (1s → 2s → 4s, max 3 retries).
The API is currently in Beta. Some functionality may change in future releases.
Gateway URL
| Environment | URL |
|---|---|
| Production (Managed Mode) | https://api.qoder.com/api/v1/cloud |
| Production (Forward Mode) | https://api.qoder.com/api/v1/forward |
Versioning
The API is currently at version v1. Endpoints use the mode-specific /api/v1/cloud or /api/v1/forward prefix; no additional version header is required.
Available APIs
| Resource | Description | Base path |
|---|---|---|
| Agents | Agent CRUD and archival | /agents |
| Environments | Runtime environment configuration | /environments |
| Sessions | Agent session creation and lifecycle | /sessions |
| Events | Session event stream reads and pushes | /events |
| Files | File upload and association | /files |
| Vaults | Secure storage for sensitive credentials | /vaults |
| Skills | Agent skill registration and management | /skills |
| Memory Stores | Persistent memory storage | /memory_stores |
| Deployments | Scheduled deployment automation | /deployments |
| Work | Self-hosted Environment work queue and worker lease lifecycle | /environments/{environment_id}/work |
| Forward Templates | Forward agent template definition, versioning, archiving, and cloning | /api/v1/forward/templates |
| Forward Identities | Forward identity creation, enable/disable, deletion, and agent lookup | /api/v1/forward/identities |
| Forward Identity Configs | Per-identity template config and effective config lookup | /api/v1/forward/identities/{identity_id}/templates |
| Forward Channels | Forward channel and QR session management | /api/v1/forward/channels, /api/v1/forward/qr_sessions |
| Forward Sessions | Forward session lifecycle, events, and SSE streams | /api/v1/forward/sessions |
| Forward Environments | Forward environment lifecycle management | /api/v1/forward/environments |
| Forward Skills | Forward Skill lifecycle management | /api/v1/forward/skills |
| Forward Vaults | Forward Vault lifecycle management | /api/v1/forward/vaults |
| Forward Credentials | Vault-scoped credential management | /api/v1/forward/vaults/{vault_id}/credentials |
| Forward Files | Forward file upload, retrieval, download, and deletion | /api/v1/forward/files |
| Forward Schedules | Forward scheduled tasks and run record management | /api/v1/forward/schedules, /api/v1/forward/schedule_runs |
Request size limits
- Maximum request body size: 4 MB
- Requests exceeding this limit are truncated, causing JSON parsing to fail with
400 invalid_request_error(message: "Request body must be valid JSON.").
Required headers
Every API request must include the authentication header; Content-Type is recommended but not mandatory — the server can auto-detect:
Beta status
- The API surface is broadly stable, but signatures may receive minor adjustments in future iterations.
- New functionality ships behind new beta identifiers.
- Lock the API version and add compatibility handling when running in production.
- When using a Beta feature, declare its identifier with
x-qoder-beta.
| Beta identifier | Surface | Guide |
|---|---|---|
browser-use-2026-07-14 | browser_toolset_20260714, browser tools, and live preview | Browser Use (Beta) |
