Authentication
Svara uses bearer API keys. Pass your key in the Authorization header on
every request:
Authorization: Bearer sk_live_...Managing keys
Create, name, and revoke keys in the console (opens in a new tab) under API keys. A key's plaintext value is shown once at creation — store it in a secret manager. If a key leaks, revoke it immediately and issue a new one.
Best practices
- Never ship keys to the browser. Call Svara from your server, or proxy requests so the key stays server-side.
- Use separate keys per environment (dev / staging / prod) so you can rotate one without disrupting the others.
- Scope usage with plans and rate limits (see Errors & Limits).
Errors
| Status | Meaning |
|---|---|
401 | Missing or invalid API key |
403 | Key valid but not permitted for this action |
429 | Rate limit, concurrency cap, or quota exceeded |