Creating a key
Under Setup → API Keys, create a key, give it a name that says what it is for, and choose its scopes. The key is shown once. Copy it then; it cannot be retrieved afterwards, only replaced.
Scopes
Read scopes let a key list and fetch. Write scopes let it create and update. Grant the narrowest set that does the job — a reporting integration almost never needs write.
Calling the API
Send the key as a bearer token against the versioned API:
curl -H "Authorization: Bearer YOUR_KEY" \
https://interviewfi.ai/api/v1/me
The full reference, with every endpoint and its shape, is at /developers/reference, and the machine-readable spec is at /api/v1/openapi.json.
The v1 prefix matters
Only routes under /api/v1 accept an API key. The internal routes the web app uses are
session-authenticated and will refuse a bearer token — that is correct behaviour rather
than a misconfiguration, and it is what keeps the two products separate.
Rate limits
Keys are rate limited per key, generously enough that ordinary batch work never trips it. Responses carry the limit and what remains, so a well-behaved client can pace itself.
If a key leaks
Revoke it immediately from the same page and create a replacement. Revocation takes effect at once. Rotate keys when the person who created them leaves, as a matter of routine rather than of suspicion.