Api reference
Authentication
All API requests authenticate with a team-scoped API key passed as a Bearer token.
Base URL
https://automette.comHeader
Authorization: Bearer dg_your_api_keyAPI keys
Keys are scoped to a single team — the team they were created under. Renders, templates, and webhooks made with a key are visible only to members of that team.
Create a key
Go to Settings → API Keys in the dashboard. Click Create key, give it a name, and copy the full secret immediately. The secret is shown only once — if you lose it, generate a new one.
Rotate or revoke a key
From the same Settings → API Keys page, click Delete next to any key to revoke it instantly. All requests using that key will start returning 401 immediately. Create a new key to replace it.
Keep keys secret
- Store keys in environment variables or a secret manager — never in source code or client-side code
- Use one key per environment (development, staging, production)
- Rotate keys if you suspect one has been exposed
Example
curl https://automette.com/api/v1/templates \
-H "Authorization: Bearer dg_your_api_key"Error responses
| Status | Meaning |
|---|---|
401 | Missing, malformed, or unrecognized Authorization header |
403 | Key is valid but does not have access to the requested resource |
404 | Resource does not exist — or it belongs to a different team. Cross-team access is indistinguishable from a missing resource by design. |
Last updated on