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

# Fix API authentication

> Check the API host, Bearer header, key status, version header, scopes, and plan when a request is rejected.

Use the exact API key shown when it was created or rotated. Redbark only displays the secret once.

## Request checklist

1. Send the request to `https://api.redbark.com/v2`.
2. Set `Authorization: Bearer rbk_live_...`.
3. Set a supported `Redbark-Version` header, as shown in the [API v2 overview](/docs/api-reference/v2/overview#required-headers).
4. Confirm the key is active and includes the scope required by the endpoint.
5. If the key was rotated, use the replacement secret. The old key expires after its grace period.

## Read the status code

| Status                          | Meaning                                                                                                       |
| ------------------------------- | ------------------------------------------------------------------------------------------------------------- |
| **400 `version_required`**      | The v2 version header is missing.                                                                             |
| **401**                         | The key is missing, malformed, revoked, expired, or otherwise invalid.                                        |
| **403 `insufficient_scope`**    | The key does not have the endpoint's required scope.                                                          |
| **403 `plan_upgrade_required`** | The current plan does not include API access. Outside a trial, API access requires Developer or Professional. |
| **403 `professional_required`** | A Developer key called a brokerage-only endpoint.                                                             |

Do not send API keys in support messages. Include the response status, error code, request method, and path instead.
