# Authentication

> Authenticate with Raywake API keys, choose scopes and expiry, revoke access and keep credentials safe in your server-side integration.

Canonical: https://raywake.si/docs/authentication
Last updated: 2026-10-13

Send your key as a bearer token on every request.

Header:

```
Authorization: Bearer $RAYWAKE_API_KEY
```

## Permissions

Each key carries only the permissions you chose when you created it. A request outside them returns `403`.

**Key permissions**

| Name | Type | Description |
| --- | --- | --- |
| `models:read` | permission | List models, read schemas and pricing. |
| `generate` | permission | Create quotes and start paid generations. |
| `jobs:read` | permission | Read generation status, results and history. |
| `wallet:read` | permission | Read available, reserved and owed funds. |

## Keep keys server-side

When you create a key, choose 30 days, 90 days, 1 year or no expiry. You can revoke any key at any time. An expired or revoked key cannot authenticate requests.

Keys spend your balance. Never ship them in browser or mobile code; call the API from your server. A new key is shown once — if it leaks, revoke it on the [API keys](https://raywake.si/api-keys) page and create another.

[Quotes and funds](https://raywake.si/docs/credits)

## Related

- [API documentation](https://raywake.si/docs)
