API keys
API keys let your app call Zevuki. Send them in the Authorization header of every request.
Authorization: Bearer zv_…
Access levels
| Access | Can do | Use it for |
|---|---|---|
| Send only | POST /v1/emails | Your app in production. If the key leaks, it can't read your email history. |
| Full access | Everything, including GET /v1/emails/{id} and managing domains with /v1/domains | Scripts and internal tools you trust. |
Keeping keys safe
- The full key is shown once, when you create it. Zevuki stores only a hash and the first characters, so nobody, including us, can show it again.
- Keep keys in environment variables or a secrets manager. Never put them in front-end code, mobile apps or public repositories.
- Use a separate key per app or environment, with a name that says where it's used. The dashboard shows when each key was last used.
- If a key may have leaked, delete it in the dashboard. It stops working immediately. Then create a new one.