> ## Documentation Index
> Fetch the complete documentation index at: https://docs.smartsend.io/llms.txt
> Use this file to discover all available pages before exploring further.
# Authentication
> Authenticate with the Smart Send REST API using bearer tokens.
The Smart Send API uses bearer tokens for authentication. Every request must include a valid API token in the `Authorization` header.
## Creating an API token
To create an API token, start by logging into the Smart Send platform .
Go to **API Tokens**.
In the **Create API Token** section, fill in a name. The name is only used for your internal classification and is not visible outside your team.
Click the **Create** button. A modal opens displaying the newly generated API token.
The API token is only shown once. Copy it and store it somewhere safe immediately. If you lose it, you will need to delete it and create a new one.
## Using your API token
Include your API token in the `Authorization` header of every request, prefixed with `Bearer`:
```bash theme={null}
curl https://app.smartsend.io/api/v2/agents/dk \
-H "Authorization: Bearer YOUR_API_TOKEN" \
-H "Accept: application/json"
```
Treat API tokens like passwords. Never commit them to version control, embed them in client-side code, or share them in support tickets. Use environment variables or a secrets manager to keep them safe.
## Revoking an API token
If a token is no longer needed or may have been exposed, revoke it immediately.
Go to **API Tokens**.
In the **Manage API Tokens** section, find the token you want to delete.
Click the **Delete** button next to the token and confirm the action.
Deleting an API token is irreversible and immediately breaks any integration that is still using it.
