Documentation

Manage API tokens

This page documents an earlier version of InfluxDB. InfluxDB v2.7 is the latest stable version. View this page in the v2.7 documentation.

InfluxDB API tokens ensure secure interaction between InfluxDB and external tools such as clients or applications. An API token belongs to a specific user and identifies InfluxDB permissions within the user’s organization.

Learn how to create, view, update, or delete an API token.

API token types

Operator token

Grants full read and write access to all organizations and all organization resources in InfluxDB OSS 2.x. Some operations, e.g. retrieving the server configuration, require operator permissions. Operator tokens are created in the InfluxDB setup process. To create an operator token manually, you must use an existing operator token.

Because Operator tokens have full read and write access to all organizations in the database, we recommend creating an All-Access token for each organization and using those to manage InfluxDB. This helps to prevent accidental interactions across organizations.

All-Access token

Grants full read and write access to all resources in an organization.

Read/Write token

Grants read access, write access, or both to specific buckets in an organization.


Was this page helpful?

Thank you for your feedback!


Set your InfluxDB URL

Introducing InfluxDB 3.0

The new core of InfluxDB built with Rust and Apache Arrow. Available today in InfluxDB Cloud Dedicated.

Learn more

State of the InfluxDB Cloud Serverless documentation

The new documentation for InfluxDB Cloud Serverless is a work in progress. We are adding new information and content almost daily. Thank you for your patience!

If there is specific information you’re looking for, please submit a documentation issue.