> 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/personal-access-tokens.md).

# Personal Access Tokens

Use a personal access token to call the Feathery REST API from your own scripts and tools.

Personal access tokens are for your own scripts and tools. Every member can create them, including Viewers. A token acts as you, so it can never do more than your role allows; see [Scopes](https://docs.feathery.io/develop/api-authentication/scopes.md#what-each-role-can-choose).

### Create a Token

1. Open your Feathery settings, go to the **Developer** tab, open **Personal access tokens**, and choose **New token**.
2. Name it after the script or tool that will use it, and choose the **Live** or **Test** mode.
3. Choose its access. Access your role doesn't allow is greyed out.
4. Choose when it expires: 30 days, 90 days, 180 days, or 1 year.
5. Click **Create** and copy the token.

{% hint style="warning" %}
The token is shown once. Store it somewhere safe, like a password manager or your tool's secret settings.
{% endhint %}

### Use a Token

Send the token as a Bearer token. Use your region's [API host](https://docs.feathery.io/develop/api-authentication.md#api-host-for-your-region):

```bash
curl https://api.feathery.io/api/form/ \
  -H "Authorization: Bearer <personal access token>"
```

Actions taken with a token appear in your organization's audit log under your name.

### Renew or Revoke a Token

You get an email 30 days and 7 days before a token expires; a 30-day token only gets the 7-day email. Tokens can't be extended, so create a new token, update your script, then revoke the old one.

To revoke a token, choose **Revoke** next to it. It stops working right away.

Tokens also stop working when they expire, when you leave the organization, or when an Admin revokes them or turns off personal access tokens. See [Admin Controls](https://docs.feathery.io/develop/api-authentication/admin-controls.md).

{% hint style="info" %}
Personal access tokens work with the REST API only. To connect an AI tool, sign in through the [MCP server](https://docs.feathery.io/develop/mcp-server.md).
{% endhint %}

### Keep It Safe

See [Security and Troubleshooting](https://docs.feathery.io/develop/api-authentication/security-and-troubleshooting.md) for best practices and fixes for common errors.


---

# 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/personal-access-tokens.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.
