Skip to main content

Qumo Deploy REST API

The Qumo Deploy REST API provides programmatic control over edge relay clusters, ephemeral token issuance, tenant lifecycle, bot machine identities, and billing.

Base URLs


Authentication

The REST API supports two authentication mechanisms depending on the endpoint category:

1. API Keys (X-API-Key)

Used for direct machine-to-machine interactions and relay token issuance (POST /api/v1/credentials). Format: qumo_live_<64 hex chars> or qumo_test_<64 hex chars>.

2. Bearer Authentication (Authorization: Bearer <token>)

Used for administrative routes under /admin/v1/, including project creation, bot management, and billing operations. Accepts:
  • Bot tokens (POST /admin/v1/projects/{project_id}/bots/{id}/keys)
  • CLI / OAuth 2.0 Device Flow tokens (qumod login)

Interactive API Playground

You can explore and execute live test requests against all REST endpoints directly within the documentation playground using the endpoints listed in the navigation menu:
  • System & Probes: /healthz, /readyz, /v1/pricing, /v1/plans
  • Authentication & Sessions: GET /admin/v1/auth/session
  • Projects & Workspaces: GET/POST /admin/v1/projects
  • Relay Credentials: POST /api/v1/credentials, POST /admin/v1/credentials/{jti}/revoke
  • Machine Identities (Bots): GET/POST /admin/v1/projects/{project_id}/bots

OpenAPI Specification File

The complete OpenAPI 3.1 schema is maintained directly in the repository at openapi.yaml.