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

# Authentication

> Authenticate Hyze Cloud API requests with a Bearer API key.

Private endpoints require an API key in the `Authorization` header.

```http theme={"system"}
Authorization: Bearer hyze_your_key
```

## Create a key

1. Open [hyzecloud.com/dashboard](http://hyzecloud.com/dashboard)
2. **Settings → API Keys → Create Key**
3. Copy the secret once (`hyze_...`)

Keys are bound to a **workspace**. Requests use that workspace’s resources.

## Example

```bash theme={"system"}
curl https://api.hyzecloud.com/api/apps/ \
  -H "Authorization: Bearer hyze_your_key"
```

With the SDK, pass the key once:

```ts theme={"system"}
import { HyzeCloud } from "@hyzecloud/sdk";

const hyze = new HyzeCloud({
  apiKey: process.env.HYZE_API_KEY,
});
```

## Best practices

* Store keys in env vars (`HYZE_API_KEY`), never in source or client-side code
* Use one key per environment or automation (CI, local, production tooling)
* Revoke keys you no longer need

## Related

* [Quickstart](/en/quickstart) — verify the key works
* [API keys endpoints](/api-reference/api-keys) — create and manage keys via API
* [Workspaces](/en/concepts/workspaces) — how multi-team access works