Skip to main content
Every request needs an API key in the Authorization header:
OpenAI SDKs send the header for you when you pass the key as api_key (Python) or apiKey (TypeScript).

Managing keys

Create and revoke keys on the API keys page of the dashboard.
  • A key starts with fr_ and is shown only once, when you create it. fastrun stores only a hash of it, so a lost key cannot be recovered; create a new one and revoke the old one.
  • You can have up to 20 active keys. Use one per app or environment so you can see their usage separately and revoke one without touching the others.
  • Keys are checked on every request, so a revoked key stops working right away.
  • Keys of a new account start working once the account has been approved.
Keep keys on the server. Don’t put them in browser or mobile app code, where anyone can read them.

When a key is refused

A missing, unknown or revoked key, or a key of an account that is not approved yet, gets 401:
If fastrun cannot check keys for a moment, it answers 503 with Retry-After: 1 rather than letting the request through. Retry it; see Errors and retries.