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

# API keys

> Create, use, and revoke API keys for the Netter public API.

API keys authenticate requests to the [public API](/docs/api/overview). Each key belongs to the user who created it and the company that was active at creation time. A key inherits that user's permissions.

## Create a key

<Steps>
  <Step title="Open API keys">
    Go to **Settings → API keys**.
  </Step>

  <Step title="Create a key">
    Give the key a descriptive name—e.g. `Production upload`—and create it.
  </Step>

  <Step title="Copy the key now">
    The full key is shown **once**, at creation. Copy it immediately and store it somewhere safe (a secrets manager). Netter only stores a hash, so a lost key can't be recovered—create a new one instead.
  </Step>
</Steps>

A key looks like this:

```
ntr_a1b2c3d4e5f6...
```

The first 12 characters (`ntr_` + 8) are shown in the dashboard so you can identify a key later without exposing the secret.

## Use a key

Pass the key as a bearer token on every request:

```http theme={null}
Authorization: Bearer ntr_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
```

See [Upload a file](/docs/api/upload-file) for a full example.

## Revoke a key

On the **API keys** page, revoke a key to disable it immediately. Any request using a revoked key returns `401 Unauthorized`. Revoking is instant and can't be undone—issue a new key if you need to rotate.

<Warning>
  Treat API keys like passwords. Never commit them to source control or embed them in client-side code. If a key leaks, revoke it and create a new one.
</Warning>