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

# API Tokens

### Overview

API tokens provide secure authentication to Transform APIs.

Use them for integrations, exports, and automations.

### Key Concepts

* **Token**: secret string used for API authentication
* **Scope**: what a token can access (configuration dependent)
* **Rotation**: replacing tokens on a schedule to reduce risk
* **Revocation**: disabling a token immediately

### How It’s Used

Use API tokens for system-to-system integration.

Use them for scheduled exports, data sync, and automated workflows.

### Benefits

* Secure automation without interactive sign-in
* Improved auditability through controlled credential ownership
* Reduced operational risk through rotation and revocation

### Setup Steps

1. Define the integration purpose and owner.
2. Create a token with a purpose-based name.
3. Store the token in a secrets manager.
4. Rotate and revoke tokens based on security policy.

Start here: [Creating and Managing API Tokens](broken://spaces/bO5MkvlsUXaVsGsjqKWy/pages/VgESexutegs3dEjn4t5T)

### Best Practices

* Use least-privilege access for token creation and storage.
* Rotate tokens on a consistent schedule.
* Revoke unused tokens immediately after decommissioning.
* Record token ownership and purpose in a controlled location.

### Summary

API tokens support secure integration and automation through controlled credentials.

Related:

* [Creating and Managing API Tokens](broken://spaces/bO5MkvlsUXaVsGsjqKWy/pages/VgESexutegs3dEjn4t5T)
* [Security and Compliance](/account-and-billing/security-and-compliance.md)

### Overview

API token creation enables secure automation and integration.

Tokens should be treated as secrets and managed with rotation and revocation.

### Key Concepts

* **Token**: secret credential used for API authentication
* **One-time display**: token values are often visible only at creation
* **Rotation**: replacing tokens on a schedule
* **Revocation**: disabling a token to stop access immediately

### How It’s Used

Create tokens for integrations that require non-interactive access.

Rotate and revoke tokens as part of security governance.

### Benefits

* Faster integration setup
* Reduced risk through controlled credential lifecycle
* Cleaner auditability for automation access

### Setup Steps

Prerequisites:

* Admin access for developer settings
* A secrets manager for storage

{% stepper %}
{% step %}

### Open API token settings

1. Navigate to developer settings.
2. Open **API Tokens**.
   {% endstep %}

{% step %}

### Create a token

1. Select **Create token**.
2. Name the token by purpose.

Use a name such as `Analytics export — weekly` or `Integration — data sync`.
{% endstep %}

{% step %}

### Copy the token value once

1. Copy the token value.
2. Store the token in a secrets manager.

{% hint style="warning" %}
Tokens are often shown only once. Treat them like passwords.
{% endhint %}
{% endstep %}

{% step %}

### Rotate or revoke

Rotate tokens on a schedule.

Revoke tokens you no longer use.
{% endstep %}
{% endstepper %}

Common issue patterns:

<details>

<summary>API Tokens is not visible</summary>

This is usually a permissions issue.

Request access from an Account Admin for developer settings.

</details>

<details>

<summary>An integration starts failing</summary>

Common causes:

* Token was revoked
* Token expired (when token expiry is enforced)
* Token is used against the wrong Account or endpoint

</details>

### Best Practices

* Use one token per integration purpose to isolate blast radius.
* Rotate tokens before planned cutovers and major releases.
* Remove tokens when the integration owner changes.

### Summary

Token lifecycle management includes naming, secure storage, rotation, and revocation.

Related: [API Tokens](/api-and-development/api-tokens.md)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.transform.ai/api-and-development/api-tokens.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.