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

# API keys

> Generate keys for the Vern REST API.

API keys let your backend run customer migrations end to end without anyone logging into the dashboard.

## Generate a key

Go to [Settings → API keys](https://app.vern.so/api-keys) and click **New key**. Give it a name (e.g. "Production server"). Copy the key — Vern doesn't show it again.

Treat it like a password. Don't commit it. Don't put it in client-side code. Use environment variables.

## Rotate or revoke

To revoke a key, open its row's menu and click **Delete**. Any request using that key fails immediately with a 401.

To rotate, create a new key, swap it in your environment, then delete the old one.

## Use it

Pass the key as an `x-api-key` header on every request:

```bash theme={null}
curl https://app.vern.so/api/v1/migrations \
  -H "x-api-key: YOUR_KEY"
```

See the [Migration API quickstart](/migration-api/quickstart) for full setup.

## What keys let you do

* Create a migration — [`POST /api/v1/migrations`](/migration-api/create-a-migration) — then upload files, run the agent, and export clean data.

Workbook-export webhook payloads are signed separately via Svix, not authenticated with API keys — see [Webhooks](/help-center/send/webhooks).

## Next

* [Migration API quickstart](/migration-api/quickstart) — make your first API call.
* [Webhooks](/help-center/send/webhooks) — receive workbook exports from Vern.