Authentication
Secret keys for your servers, live and test, and how to roll or revoke one.
Every /v1 request carries a secret key in the Authorization header. Keys are made in the dashboard, on the API keys page, by an owner or an admin of your organization.
curl https://api.daxov.com/v1/characters \
-H "Authorization: Bearer $ACME_SECRET_KEY"The word Bearer is case-sensitive. A missing, wrong or revoked key is 401 invalid_api_key; so is any key of an organization that has been disabled.
Two kinds of key
| Key | Starts with | For |
|---|---|---|
| Secret | sk_live_, sk_test_ | Your servers: /v1 and the MCP server |
| Publishable | pk_live_, pk_test_ | The website widget only. /v1 answers it 401 |
A key is its prefix followed by 40 random letters and digits. It is shown once, when it is made: copy it then. We keep only a peppered hash of it, and list it by its last four characters.
Keep secret keys on your server
There is no CORS on /v1, so a browser can't call it, on purpose. A secret key never belongs in a web page or an app someone can download. The browser gets only what a call needs: see Calls.
Live and test keys
A live key runs real calls, charged at the price of the character's tier. A test key runs real calls too, with these differences:
- Never charged.
- Short. Each call is at most 60 seconds, and a meeting too.
- Counted. 20 calls per organization in any 24 hours, then 429
test_limit. - Its own env. A test key sees and makes only test webhook endpoints, test memories and test analytics, and lists, reads and ends only test calls and test meetings. A live call or meeting is 404
not_foundto it, as if it didn't exist; asking for live memories or analytics is 400invalid_field. A live key is the same the other way round. - Shared assets. Characters, documents, guardrail sets, pronunciation dictionaries, tools, MCP servers and cloned voices are the organization's, so both kinds of key see the same ones.
Use a test key while you build your integration, then switch the key, not the code.
Rolling and revoking
Both are on the dashboard's API keys page.
- Revoke stops a key at once: every request reads the key's row, so the next one is refused.
- Roll makes a new secret for the same key. The old secret keeps working for the grace time you choose, from 0 seconds up to 7 days (604,800 seconds), so you can switch your servers over without a gap. A key and its rolled-over old secret share one rate limit.
The MCP server takes the same keys
Our MCP server at https://api.daxov.com/mcp reads a secret key exactly as /v1 does, with the same env: a test key there sees and makes only test things.