x-api-key header, except the unauthenticated infrastructure endpoints (/health, /ready, /status, /metrics).
How to authenticate
Pass your API key in thex-api-key request header:
API key metadata
Each API key resolves to a client and its access rules:
Your API key determines which accounts, orders, and bets you can access. All data is filtered by your
clientName.
WebSocket authentication
For WebSocket connections, authenticate via the login message after connecting (the/ws endpoint itself does not require the x-api-key header):
Rate limiting
Requests are rate-limited per client — by default 100 requests per second, with a maximum of 5 concurrent WebSocket connections per API key. Full detail, headers, and backoff guidance live in Rate limits.Error responses
The auth middleware emits errors under an
error key, while application-level errors (validation, not-found, etc.) use the FastAPI-standard detail key. Handle both shapes.Next steps
Quickstart
Place your first bet in 5 steps.
Limits & Reliability
Per-client rate limits, circuit breakers, and emergency mode.