en-api-authentication.md
Every OmniaKey API request uses an API key from the API Keys dashboard.
The universal form is an Authorization header:
Authorization: Bearer your-omniakey-api-key
Use this form for cURL, OpenAI-compatible clients, and most custom integrations.
Official SDKs use different auth conventions. OmniaKey accepts the common forms for the protocol being called.
| SDK or protocol | Auth form |
|---|---|
| OpenAI SDK | api_key / Authorization: Bearer |
| Anthropic SDK | api_key / x-api-key |
| Gemini SDK | api_key / x-goog-api-key / ?key= query parameter |
For custom integrations, prefer Authorization: Bearer. It works consistently across all documented endpoints.
Create separate keys for local development, CI, and shared team workflows. This makes it easier to rotate a compromised key and set per-key spending caps.
| Status | Meaning | Fix |
|---|---|---|
401 | Missing, inactive, or invalid key | Create or rotate the key in the dashboard |
403 | Key cap or account balance is too low | Raise the key cap or top up balance |
API OverviewOpenAI-compatible API
⌘I