> For the complete documentation index, see [llms.txt](https://docs.feathery.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.feathery.io/develop/api-authentication/api-keys.md).

# API Keys

Use or rotate a Live or Test mode API key, and move integrations off API keys.

{% hint style="warning" %}
API keys are deprecated. They have full access to their mode and never expire. Use an OAuth app or a personal access token instead.
{% endhint %}

Each mode (Live and Test) has its own API key that can do everything in that mode. API keys still work, but they can't be limited to certain areas and never expire. For new work, use an [OAuth app](https://docs.feathery.io/develop/api-authentication/api-clients.md) or a [personal access token](https://docs.feathery.io/develop/api-authentication/personal-access-tokens.md).

### Use an API Key

Admins and Editors can copy the API key for each mode from **SDK and API keys** in the **Developer** tab. Send it with the `Token` prefix:

```bash
curl https://api.feathery.io/api/form/ \
  -H "Authorization: Token <API key>"
```

Responses to requests made with an API key include a `Deprecation` header and a `Link` header that points to the [API Authentication](https://docs.feathery.io/develop/api-authentication.md) page.

Don't confuse it with the SDK key, which embeds forms in your site and is public.

### Rotate an API Key

Rotate an API key through the API, using the key itself. Rotating needs the Growth or Business plan.

```bash
curl -X PATCH https://api.feathery.io/api/account/rotate_key/ \
  -H "Authorization: Token <API key>"
```

The response has `old_api_key` and `new_api_key`. The old key stops working right away, so update every integration that uses it at the same time.

### Move Off API Keys

1. Create an [OAuth app](https://docs.feathery.io/develop/api-authentication/api-clients.md) for each integration that uses the API key, with only the access it needs.
2. Switch each integration to the OAuth app. If it calls `GET /api/form/submission/batch/<form_id>/` or `/api/form/hidden_field/`, move it to `GET /api/form/submission/` or `/api/field/hidden/` too; the older endpoints only accept an API key.
3. Once nothing uses the key, an Admin can [turn off API keys](https://docs.feathery.io/develop/api-authentication/admin-controls.md#turn-off-api-keys).

Some things still need an API key: Zapier, Power Automate, MCP connections set up with an API key, and integrations that work inside child workspaces.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.feathery.io/develop/api-authentication/api-keys.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
