> ## Documentation Index
> Fetch the complete documentation index at: https://www.tella.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Create and manage API keys

> Create and revoke Tella API keys in Settings → API Keys (under Other). Each key is shown once, you can have up to 10, and Viewers can't open the page.

You create and revoke Tella API keys in **Settings** → **API Keys**, under **Other**: click your **workspace name** in the top-left corner, then **Settings**. Each key is shown only once, and you can have up to 10 at a time.

An API key authenticates requests to Tella on your workspace's behalf. You need one for the [public API and webhooks](/docs/help/integrations/public-api-and-webhooks) and for skills that call Tella, such as [Tella to YouTube](/docs/help/integrations/tella-to-youtube-agent-skill). The [Tella MCP server](/docs/help/integrations/mcp-server) usually signs in with OAuth instead, but also accepts an API key.

<Note>
  Members with the Viewer role cannot open this page. Ask a workspace owner or member to create a key for you.
</Note>

## Create a key

1. Go to **Settings → API Keys**.
2. Click **Create key**.
3. In **Create API key**, give the key a name that says where it will be used, for example, `Production API key`. The name is only a label for you; it does not affect what the key can do.
4. Click **Create**.
5. Copy the key straight away and store it somewhere safe.

<Warning>
  The full key is shown once, at the moment you create it. Tella cannot show it to you again. If you lose it, revoke the key and create a new one.
</Warning>

## What does the key list show?

Each key in the table shows:

* **Name:** the label you gave it.

* **Key:** the first few characters of the key. This prefix is enough to tell keys apart, but it is not the key itself.

* **Created:** when the key was made.

* **Last used:** when a request last used it, or **Never** if nothing has used it yet.

**Last used** is the quickest way to find keys you can safely retire: anything that says **Never**, or that has not been used in months, is a good candidate to revoke.

## Revoke a key

1. Find the key in the table.
2. Click **Revoke**.
3. Confirm.

Revoking takes effect immediately, and **any application still using that key stops working**. If a script or integration breaks right after you revoke, that is why. Issue a new key and update the integration with it.

## How do I keep API keys safe?

* Treat a key like a password. Anyone holding it can act on your workspace through the API.

* Do not commit keys to a repository, paste them into a prompt, or share them in chat.

* Use a separate key per integration, so you can revoke one without breaking the others.

## Is there a limit on API keys?

Yes. You can have up to 10 API keys at a time. If creating a key fails with "Maximum of 10 API keys allowed per user", revoke one you no longer use and try again.

## Use your key

For how to send the key with a request, see the [authentication guide](/docs/authentication) in the developer documentation.


## Related topics

- [Does Pro include API and MCP access?](/docs/help/faq/does-pro-include-api-and-mcp.md)
- [Set up webhooks](/docs/help/integrations/set-up-webhooks.md)
- [AI onboarding](/docs/ai-onboarding.md)
- [Create a webhook endpoint](/docs/api-reference/webhooks/create-a-webhook-endpoint.md)
- [Public API and webhooks](/docs/help/integrations/public-api-and-webhooks.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.