API reference
Authentication
Every DunOps API request is authenticated with a long-lived API key. Keys are scoped to a workspace and carry the permissions of the owner who created them.
Note
API access is available on the Pro plan and above. Hobby workspace users can explore the docs but API keys won't work.
Generate an API key
- 1. Go to Settings → API keys.
- 2. Click New key, give it a name (e.g.
ci-deploy). - 3. Copy the key immediately — it's shown only once. If you lose it, revoke it and generate a new one.
Request format
Pass the key in the Authorization header as a Bearer token:
curl
curl https://api.dunops.com/v1/workspaces/me \
-H "Authorization: Bearer dk_live_..."API keys look like dk_live_ followed by a random string. Test keys (for staging environments) start with dk_test_.
| Header | Value |
|---|---|
Authorization | Bearer dk_live_... |
Content-Type | application/json (required for POST/PATCH) |
DunOps-Version | 2026-01-01 (optional; pins the API version) |
Security tips
Warning
Never put API keys in client-side code or public repositories. Use environment variables in your CI/CD pipeline.
Rotate keys periodically — revoke from Settings → API keys and issue a new one. Keys don't expire automatically but can be revoked at any time.