> 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.md).

# API Authentication

Choose how to authenticate to the Feathery REST API: OAuth apps, personal access tokens, or API keys.

Every request to the [Feathery REST API](https://api-docs.feathery.io/#introduction) needs a credential. You create them in the **Developer** tab of your Feathery settings.

|                      | [OAuth apps](/develop/api-authentication/api-clients.md)    | [Personal access tokens](/develop/api-authentication/personal-access-tokens.md) | [API keys](/develop/api-authentication/api-keys.md) |
| -------------------- | ----------------------------------------------------------- | ------------------------------------------------------------------------------- | --------------------------------------------------- |
| **Best for**         | Servers and integrations                                    | Your own scripts and tools                                                      | Existing integrations (deprecated)                  |
| **Belongs to**       | The organization                                            | You                                                                             | A mode (Live/Test)                                  |
| **Who creates them** | Admins                                                      | Any member                                                                      | Created with each mode (Live/Test)                  |
| **What it can do**   | The access you choose                                       | The access you choose, limited by your role                                     | Everything in its mode (Live/Test)                  |
| **Expires**          | Secrets after 90 days to 1 year; access tokens after 1 hour | After 30 days to 1 year                                                         | Never                                               |
| **Header**           | `Authorization: Bearer <access token>`                      | `Authorization: Bearer <token>`                                                 | `Authorization: Token <API key>`                    |

### Which to Use

* **An integration or server that runs on its own:** create an [OAuth app](/develop/api-authentication/api-clients.md).
* **Your own scripts or tools:** create a [personal access token](/develop/api-authentication/personal-access-tokens.md).
* **An integration that already uses an API key:** it keeps working. Move it to an OAuth app when you can; see [API Keys](/develop/api-authentication/api-keys.md).
* **An AI tool:** connect through the [MCP server](/develop/mcp-server.md) and sign in with your Feathery account.

OAuth apps and personal access tokens only reach the areas you choose and expire on their own, so a leaked credential reaches less and stops working sooner.

{% hint style="info" %}
The developer API requires a paid plan.
{% endhint %}

### API Host for Your Region

| Region | API host                     |
| ------ | ---------------------------- |
| US     | `https://api.feathery.io`    |
| CA     | `https://api-ca.feathery.io` |
| EU     | `https://api-eu.feathery.io` |
| JP     | `https://api-jp.feathery.io` |
| AU     | `https://api-au.feathery.io` |

### In This Section

| Page                                                                                        | What it covers                                                           |
| ------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------ |
| [OAuth Apps](/develop/api-authentication/api-clients.md)                                    | Create an OAuth app, get access tokens, and rotate secrets               |
| [Personal Access Tokens](/develop/api-authentication/personal-access-tokens.md)             | Create, use, renew, and revoke your own tokens                           |
| [API Keys](/develop/api-authentication/api-keys.md)                                         | Use and rotate API keys, and move off them                               |
| [Scopes](/develop/api-authentication/scopes.md)                                             | Access areas, scope names, and what each role can choose                 |
| [Admin Controls](/develop/api-authentication/admin-controls.md)                             | Reviewing members' tokens, turning tokens or API keys off, expiry emails |
| [Security and Troubleshooting](/develop/api-authentication/security-and-troubleshooting.md) | Best practices, credential prefixes, and common errors                   |

### Current Limitations

* **Child workspaces:** OAuth apps and personal access tokens can't act inside child workspaces yet. To work inside one, use that workspace's API key, which workspace details only include for requests made with an API key.
* **A few endpoints:** rotating the API key, `GET /api/form/submission/batch/<form_id>/`, and `/api/form/hidden_field/` only accept an API key. Use `GET /api/form/submission/` and `/api/field/hidden/` instead of the last two.
* **Zapier and Power Automate:** both connect with an API key.
* **MCP:** OAuth apps and personal access tokens don't work with the MCP server. Connect AI tools by signing in.


---

# 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.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.