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

# API Tokens

API Tokens allow your organization to authenticate automated workflows and access the Appetize REST API.

You can manage your organization's API tokens by navigating to [**Organization → API Tokens**](https://appetize.io/organization/api-tokens)

{% hint style="warning" %}
Tokens belong to the organization, not to individual users. 

If a user who generated a token is removed from the organization, the token continues to work.
{% endhint %}

***

## Generating an API Token

Admins can create a new token by selecting **Generate API Token**.

You will be asked to provide:

* **Label**\
  A short name that identifies how this token will be used, such as a CI system, a script, or an internal tool. The label helps you recognize activity created by this token. We recommend not reusing the same label twice.
* **Role**\
  Choose the level of access the token should have.\
  Pick the least-privileged role that matches your automation’s needs.

Select **Generate Token** to create it.

<figure><img src="https://2147444700-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MJUveBCJfn0GR8-hlqi%2Fuploads%2F6Fy1aqXS2TG8n5luQlOM%2Fimage.png?alt=media&amp;token=ceed3724-bead-42a7-aa51-6b02ad99fbb1" alt=""><figcaption></figcaption></figure>

After the token is created:

* The full token appears once. Copy and save it securely, because it cannot be viewed again.
* All organization admins will receive an email with the creator, the time it was generated, and an obfuscated version of the token.

<figure><img src="https://2147444700-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MJUveBCJfn0GR8-hlqi%2Fuploads%2FRKq9kibru5OnkvLrB5Qj%2Fimage.png?alt=media&amp;token=b298e18d-4690-43a1-929b-2e47a73250d6" alt=""><figcaption></figcaption></figure>

***

## Viewing Tokens

<figure><img src="https://2147444700-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MJUveBCJfn0GR8-hlqi%2Fuploads%2FCsv8FM1CAWbtp2Fk0KWv%2Fimage.png?alt=media&amp;token=30b6d0db-6d4d-41f6-bb4f-b2f60fbaaf6b" alt=""><figcaption></figcaption></figure>

Admins can view all API Tokens in the organization. Each token displays:

* **Label**\
  The name given when the token was created, useful for identifying where the token is used.
* **Token**\
  A partially masked version of the token, shown for reference only. The full token is never displayed again after creation.
* **Last used**\
  Indicates the most recent time the token authenticated a request.
* **Created by**\
  Shows who originally generated the token.&#x20;
* **Role**\
  Indicates whether the token was created with Developer or Admin privileges.
* **Delete icon**\
  Allows an admin to revoke the token.

***

## **Revoking Tokens**

To revoke a token, select the bin icon next to it.\
A confirmation dialog appears and you will be asked to type the token’s label to confirm the removal.

<figure><img src="https://2147444700-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MJUveBCJfn0GR8-hlqi%2Fuploads%2F80DunKcS9OnSmehuAFLh%2Fimage.png?alt=media&amp;token=aeaf096c-9ac9-423d-b20e-63e215fca557" alt=""><figcaption></figcaption></figure>

Once a token is revoked, any integrations using this token will lose its functionality immediately.