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

# Authentication

> Create an API key and use it to call the API

Every request carries an API key. The key belongs to your workspace, so no path or parameter names one.

## Create an API key

**1. Open the API settings**

In ReachHunt, open [**Settings → API**](https://app.reachhunt.ai/settings/api).

**2. Create the key**

Select **New API key**, give it a name you will recognize, such as `Zapier production`, and select **Create key**. A name can be up to 40 characters.

**3. Copy it now**

The key is shown once. Copy it and store it somewhere safe. If you lose it, delete the key and create a new one.

You need full access to every section of the workspace to create, rename or delete keys.

## Use the key

Send it in the `Authorization` header of every request:

```txt theme={"system"}
Authorization: Bearer YOUR_API_KEY
```

```bash cURL theme={"system"}
curl "https://api.reachhunt.ai/api/v1/tags" \
  -H "Authorization: Bearer YOUR_API_KEY"
```

## What a key can do

A key belongs to one workspace and acts as the workspace owner, with full access to it. To work with another workspace, create a key in that workspace.

A key cannot change who has access, so these are refused:

* Creating, renaming or deleting API keys.
* Billing and payments.
* Your own profile and sign-in.
* Creating, renaming, switching or deleting workspaces, and managing members and invites. Reading them is allowed.

A refused request returns `status: false` with the error `API keys cannot be used for this request`.

## Failures

| Response | Cause |
| - | - |
| `401` | The header is missing, or the key is not valid or was deleted |
| `402` | The workspace has no active plan, or its trial has ended |
| `200` with `status: false` | The key cannot be used for this request, or the request itself was refused. Read `error` |

All of them come back in the usual [response envelope](https://docs.reachhunt.ai/developer-api/response-format.md) with `status` set to `false`. See [Errors](https://docs.reachhunt.ai/developer-api/errors.md) for every status code.

## Keys made by integrations

When you connect an AI app through the [MCP server](https://docs.reachhunt.ai/integrations/mcp-server.md), ReachHunt creates a key for it, named after the app with `(MCP)` after it. Delete that key to disconnect the app.

## Rotate or revoke a key

Create a new key, switch your integration to it, then delete the old one in [**Settings → API**](https://app.reachhunt.ai/settings/api). A deleted key stops working right away. Keys are also revoked when the workspace is deleted.


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