Auth & API Keys
Bearer tokens, key rotation, IP allowlists, and the errors you'll see when auth goes wrong.
Bearer tokens
Every request to https://api.eveses.com carries an API key as a bearer token:
Authorization: Bearer 17|aBcDeFgHiJkLmNoPqRsTuVwXyZ0123456789abcd
Keys are created in Account → API Keys. Treat them like passwords — they grant full access to wallet balance, activations, rentals.
Create
Click New key, give it a label (local-dev, ci, production-eu). The token is shown once on creation — store it immediately.
Rotate
Keys are not editable. To rotate: create a new key → swap into your deployment → delete the old one. Deletion is immediate.
IP allowlist
Per-key allowlist: tie a key to specific IPs / CIDR ranges. Requests from outside the list get 403. Configure on the key's detail page.
Scopes
All keys currently grant full account access. Per-scope keys (read-only, rentals-only) are on the roadmap.
Errors
| HTTP | Meaning |
|---|---|
| 401 | Missing or malformed Authorization header |
| 403 | Key revoked, account suspended, or IP not on allowlist |
| 429 | Per-key rate limit exceeded (default 60 rpm) |