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

# Authentication

> Authenticate gHypurr API requests with the Bearer header.

Send the API key in the standard `Authorization` header:

```http theme={"dark"}
Authorization: Bearer YOUR_API_KEY
```

The header must contain exactly one Bearer credential. Do not send the key as a
query parameter or JSON field.

## Example

```bash theme={"dark"}
curl "https://ghypurr.com/api/v1/smart-wallets?lane=ready&limit=20" \
  -H "Authorization: Bearer YOUR_API_KEY"
```

Authentication can fail when a key is malformed, revoked, expired, belongs to
an account without current API access, does not include the required scope, or
does not permit the request IP.

| Status | Error                | Meaning                                                    |
| ------ | -------------------- | ---------------------------------------------------------- |
| `401`  | `invalid_api_key`    | The Bearer key is absent, malformed, inactive, or invalid. |
| `403`  | `insufficient_scope` | The key lacks the endpoint's required scope.               |
| `403`  | `ip_not_allowed`     | The request source is outside the key's allowlist.         |

Error responses use this shape:

```json theme={"dark"}
{
  "error": "invalid_api_key",
  "message": "API key is invalid or inactive"
}
```