Create and manage API keys
Create an API key for the Embeddable Developer API, send it with your requests, and revoke or rotate it safely.
API keys let your own code call the Embeddable Developer API for your workspace. You create and manage them in the app.
Create a key
- Sign in to your Embeddable workspace.
- Open Settings, then select the For developers tab. This opens the API Keys page.
- Make sure the Keys toggle is selected (the other option is Usage).
- Click New API Key and give the key a name.
- Copy the full key shown. You won't be able to see it again, so store it somewhere safe right away, like you would a password.

Your key starts with emb_live_. Each key belongs to one workspace. A key from one workspace can't read or change anything in another.
Authenticate requests
Send your key in an Authorization header with the Bearer scheme on every request. The base URL is https://api.embeddable.co/v1.
curl https://api.embeddable.co/v1/widgets \
-H "Authorization: Bearer emb_live_..."
If authentication fails, the API returns JSON in the form { "error": "<code>", "message": "<human readable>" }:
| HTTP status | error | When it happens |
|---|---|---|
| 401 | unauthorized | The Authorization header is missing or malformed |
| 401 | invalid_key | The key isn't recognized, was revoked, or is in the wrong format |
A 401 with invalid_key after your key worked before usually means someone revoked it.
To see how many API tokens your requests have used, open the Usage toggle on the same page. Creating a widget, editing a widget, creating an agent and running an agent each use 1 token. Reading, listing, deleting and publishing use none.
For endpoints and request bodies, click API Documentation on the API Keys page.
Revoke or rotate
Manage existing keys from the Keys toggle on the API Keys page under Settings > For developers. Revoke a key from this page if it leaks or you no longer need it. Once revoked, requests that use it fail with a 401 and invalid_key.
To rotate a key without downtime:
- Click New API Key and create a replacement.
- Update your code or secret store to use the new key.
- Confirm your requests succeed with the new key.
- Return to the API Keys page and revoke the old key.
Did this answer your question?
Your feedback helps us improve.
