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

# Authentication

> Authenticate API requests with a Parley API key.

Send your API key as a Bearer token in the `Authorization` header of every request:

```bash theme={null}
curl https://api.parley.so/v1/projects \
  --header "Authorization: Bearer $PARLEY_API_KEY"
```

## API keys

An API key belongs to one user in one organization. Requests made with it act as that user and see only the records that user can see.

Only members of your firm can use the API. Client users can't, and their requests return `403 FORBIDDEN`.

To get an API key, [contact the Parley team](/help/getting-support.md).

> [!WARNING]
>
> Treat an API key like a password. Keep it out of source control and client-side code, and store it in a secret manager or an environment variable.

## Authentication errors

| Status | Code | Meaning |
| - | - | - |
| `401` | `UNAUTHORIZED` | The `Authorization` header is missing, or the key is invalid or revoked. |
| `403` | `FORBIDDEN` | The key's user isn't allowed to use the API. |
| `429` | `TOO_MANY_REQUESTS` | Too many attempts to validate a key. Wait briefly and retry. |


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