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

# Authentication

> Send your API key in the X-API-Key header.

Every request needs your API key in the `X-API-Key` header.

```bash theme={null}
curl "https://api.salessequencer.com/api/v1/me" \
  -H "X-API-Key: YOUR_API_KEY"
```

| Problem | Response |
| - | - |
| No header | `401` `{"error": "missing X-API-Key header"}` |
| Wrong or revoked key | `401` `{"error": "invalid or revoked API key"}` |

## Who a key acts as

A key belongs to one workspace and to the person who created it. Every call:

* runs **as the key's creator**,
* with **that user's role** in the workspace (checked on every call, so changing their role changes what the key can do),
* **in the key's workspace**.

See [workspaces and roles](https://docs.salessequencer.com/concepts/workspaces-and-roles.md) for what each role can do.

## Managing keys

* Workspace admins create and revoke keys in the app under the workspace's **API keys** settings, or with the [API keys endpoints](https://docs.salessequencer.com/api-reference/api-keys/create-an-api-key.md).
* The key is shown once when it's created. Only a hash is stored, so a lost key can't be recovered; revoke it and create a new one.
* Revoking a key takes effect on the next request.

## Keep your key safe

* Call the API from your server or workflow tool, never from a browser.
* Store the key in an environment variable or a secrets manager.
* A key can send email from your mailboxes. Treat it like a password.


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