Documentation

Manage API tokens

This page documents an earlier version of InfluxDB OSS. InfluxDB 3 Core is the latest stable version.

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–for example, retrieving the server configuration–require operator permissions.

Initial operator token

When you first initialize InfluxDB, the setup process creates an initial user, org, bucket, and an Operator token with full read/write access to all organizations. When running setup, you can either:

  • Supply the token value yourself (influx setup --token flag or the setup API token field), or
  • Let InfluxDB auto-generate it. InfluxDB stores the generated token in the active influx CLI config so the CLI can use it later.

Creating operator tokens after setup

To create an operator token manually with the InfluxDB UI, api/v2 API, or influx CLI after the setup process is completed, you must use an existing Operator token.

To create a new Operator token without using an existing one, see how to use the influxd recovery auth CLI.

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!


Telegraf Enterprise now in public beta

Get early access to the Telegraf Controller and provide feedback to help shape the future of Telegraf Enterprise.

See the Blog Post

The upcoming Telegraf Enterprise offering is for organizations running Telegraf at scale and is comprised of two key components:

  • Telegraf Controller: A control plane (UI + API) that centralizes Telegraf configuration management and agent health visibility.
  • Telegraf Enterprise Support: Official support for Telegraf Controller and Telegraf plugins.

Join the Telegraf Enterprise beta to get early access to the Telegraf Controller and provide feedback to help shape the future of Telegraf Enterprise.

For more information:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On May 27, 2026, the latest tag for InfluxDB Docker images will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments.

If using Docker to install and run InfluxDB, the latest tag will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments. For example, if using Docker to run InfluxDB v2, replace the latest version tag with a specific version tag in your Docker pull command–for example:

docker pull influxdb:2