Authentication

Sign in, select your team, and open Settings → API keys. Give each integration a descriptive name. Copy the secret into your server environment. Team owners and admins can reveal or copy keys again in settings.

API keys belong to a team. Your integration uses that team's plan and usage allowance, independently of which team you select in the website later.

Send your key in the Authorization header using the Bearer scheme. Use HTTPS. Keep keys in server-side environment variables; never put them in browser code, query strings, or a public repository.

For the interactive rate and account examples, choose a key in the API key menu in the navigation. Your most recently created, recoverable key is selected automatically. The code preview masks the secret; Copy inserts your selected key into the authenticated command. Without a selected key, interactive examples use the FEEBASE_API_KEY environment variable.

Use Run request to send the request and inspect its HTTP status, duration, and actual JSON response. Keys are loaded only when you copy or run; they are not stored in documentation page props or browser storage.

GET /api/v1/me returns the team, key metadata, current plan, and monthly usage. This endpoint works without an active paid plan. It is rate-limited but is not counted as a billable lookup.

See the account endpoint reference for the complete response fields and an example. The response does not return your full API key. A missing or revoked key returns HTTP 401 with a JSON message.

Create a replacement, update your integration, and verify a request before revoking the old key. Revoke unused or exposed keys in team settings. Never send a secret key when asking for support.