Base URL
All API requests are made to:Authentication
Every request requires aAuthorization: Bearer header with either a Personal Access Token (PAT) or a JWT.
X-Workspace-Id header:
Authentication Guide
Learn how to create tokens, authenticate with the CLI, and use JWTs
Conventions
The API usessnake_case for all field names. This keeps responses consistent regardless of the client language and matches the format you see in curl, logs, and debugging tools.
Response Format
Single objects are returned directly — no wrapper:data with pagination:
error envelope:
Pagination
List endpoints support cursor-based pagination with two query parameters:| Parameter | Type | Default | Description |
|---|---|---|---|
limit | integer | 50 | Items per page (1-100) |
cursor | string | — | Cursor from a previous response |
Error Codes
| HTTP Status | Code | Description |
|---|---|---|
| 400 | bad_request | Malformed request |
| 401 | unauthorized | Missing or invalid token |
| 403 | forbidden | Not a member of the workspace |
| 404 | not_found | Resource does not exist |
| 409 | conflict | Resource already exists |
| 422 | validation_error | Request body failed validation |
| 500 | internal_error | Unexpected server error |
Interactive Docs
The API spec is also available as an interactive reference powered by Scalar:Scalar API Reference
Interactive API explorer with request builder
OpenAPI Spec
Raw OpenAPI 3.1 specification (JSON)
Next Steps
Authentication
Create tokens and learn about supported auth methods
CLI
Install the CNAP CLI for terminal-based workflows
Platform MCP
Let AI agents call the API through Code Mode
AI & Agents
Connect AI tools to CNAP docs and infrastructure