GET /v1/health and GET /v1/ready) must carry an API key.
Sending your key
Two header forms are accepted.Authorization: Bearer is preferred:
Key format
Keys look likefa_live_ followed by 40 hex characters — 48 characters in total:
- The full key is displayed exactly once, at creation. Only a SHA-256 hash is stored server-side, so a lost key cannot be recovered — revoke it and create a new one.
- In the dashboard and in usage reports, keys are identified by their first 12 characters (for example
fa_live_7fb3).
Managing keys
Keys are managed in the dashboard under Settings → API keys:- Create — optionally give the key a name (up to 80 characters) describing where it’s used. You can hold up to 5 active keys.
- Revoke — takes effect immediately. Revoked keys return
401on their next request.
Security best practices
- Server-side only. The API enforces a server-to-server CORS policy — browsers cannot call it from arbitrary web origins, and keys must never ship in client-side code, mobile apps, or public repositories.
- Use environment variables or a secret manager; never hardcode keys in source.
- Rotate on exposure. If a key leaks, revoke it in the dashboard immediately and create a replacement — revocation is instant.
- One key per integration. Scoped keys make rotation and usage attribution painless.
Request IDs
Every response includes a request identifier. Send your ownX-Request-ID header to correlate requests with your logs, or let the API generate one. Include it when contacting support@focusalpha.ai — it lets us trace the exact request.
Related pages
Plans & credits
What each plan unlocks and how calls are metered.
Rate limits
Per-key request budgets by plan.