API keys and authentication
Every request carries one of your API keys. All your keys share your account's plan.
Sending the key
Send the key as a bearer token:
Authorization: Bearer fdb_…
X-API-Key: fdb_… works too. Keys in the URL are refused, as they'd end up in logs. A missing, unknown or revoked key gets a 401, and so does any key until your e-mail address is confirmed.
Managing keys
Create keys on the API keys page, up to 20 at once. Each shows when it was last used.
A key is shown only once. If you lose it, revoke it and create a new one; a revoked key stops working immediately.
Keeping keys safe
- Keep keys on your servers. A key shipped in a web page or mobile app belongs to everyone who uses it.
- Use one key per app, so you can revoke one without breaking the others.
- If a key leaks, revoke it first and replace it in your app second. The order matters.
AI assistants sign in with your account instead, and never see your keys. See Connect an AI assistant.