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

# Authentication

> How to authenticate requests to the Grow CRM API.

# Authentication

Every Grow CRM API request is authenticated with an **API key**, sent as a Bearer token in the
`Authorization` header:

```
Authorization: Bearer YOUR_API_KEY
```

## Obtaining a key

API keys are created inside the CRM under **Settings → API Keys**. Give the key a name and the
system generates its value. Treat the key like a password — anyone with it has full API access.

## Privileges

All API keys are **administrator-level**: a valid key runs with full privileges as the CRM's
**main administrator**. There are no user-scoped keys.

Where an action supports per-record attribution, you can set it explicitly in the payload — for
example `project_creatorid` when creating a project (it defaults to the main administrator if
omitted).

## Multitenant (SaaS)

On the multitenant edition, call the API on **your own account domain**:

```
https://your-domain/api/...
```

The domain identifies your account, and the API key is validated against your account's data.
No account identifier is needed in the key or the URL.

## Errors

| Status             | Meaning                            |
| ------------------ | ---------------------------------- |
| `401 Unauthorized` | The API key is missing or invalid. |

```json theme={null}
{
  "message": "Unauthorized. A valid API key is required."
}
```