> ## Documentation Index
> Fetch the complete documentation index at: https://client-integrations-api-dev.sequen.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Authentication

> Authenticating requests to the Sequen API using API Keys.

# API Authentication

All Sequen API endpoints require authentication. Authentication is performed using API keys passed in the HTTP `Authorization` header as a Bearer token.

## Finding Your API Key

You can find your API key in the Sequen Dashboard under **Settings > API Keys**.

<Note>
  API keys are intended for server-to-server authentication only. Never expose your API key in client-side code (browsers, mobile apps) or commit it to version control. Store it securely in environment variables or secrets management systems on your backend servers.
</Note>

## Using the API Key

To authenticate your requests, include your API key in the `Authorization` header as a Bearer token:

```http Request Header theme={null}
Authorization: Bearer YOUR_API_KEY
```

Replace `YOUR_API_KEY` with your actual Sequen API key.

## Legacy Authentication Method

Older client versions may use the `X-API-Key` header for authentication:

```http Request Header theme={null}
X-API-Key: YOUR_API_KEY
```

<Note>
  If you're unsure which authentication method to use, please check with the Sequen team to determine the appropriate method for your integration.
</Note>

## Example Request

Here's an example using `curl` to make an authenticated request (replace with a real endpoint later):

```bash Example Curl Request theme={null}
curl -X GET https://api.sequen.com/v1/some-endpoint \ # Replace with a valid endpoint
  -H "Authorization: Bearer YOUR_API_KEY" 
```

If the API key is missing, invalid, or expired, the API will return a `401 Unauthorized` error.