Documentation

Manage tokens

InfluxDB 3 Cloud uses token-based authorization to authenticate and authorize actions in your instance.

Manage InfluxDB 3 Cloud tokens with the influxdb3 CLI

In InfluxDB 3 Cloud, you create and manage tokens with the influxdb3 CLI or the InfluxDB HTTP API.

Token types

InfluxDB 3 Cloud supports the following token types:

  • Admin tokens: Grant full administrative access to all actions and resources in the instance.
    • Operator token: The first admin token on an instance. InfluxData manages the operator token for your InfluxDB 3 Cloud instance.
      • Never expires
      • Cannot be edited or deleted
    • Named admin tokens: Additional admin tokens that you create and manage.
      • Can be created, edited, and deleted
      • Long-lived by default and expire only if you set an expiration
      • Cannot modify or remove the operator token
  • Database tokens: Grant scoped read and write access to specific databases. Use database tokens to authorize applications that write or query data.
    • Grant read, write, or both to one or more databases
    • Cannot perform administrative actions

Store secure tokens in a secret store

Token strings are returned only when you create the token. Store tokens in a secure secret store. Anyone with access to an admin token has full control over your InfluxDB 3 Cloud instance. If you lose a token string, recreate the token.

Create a token

Before you create tokens:

Create a named admin token:

influxdb3 create token --admin --name "support-2026"

To set an expiration, add --expiry with a duration (for example, 90d or 1y):

influxdb3 create token --admin --name "temp-90d" --expiry 90d

Create a database token with scoped read and write permissions:

influxdb3 create token \
  --permission "db:
DATABASE_NAME
:read,write"
\
--name "Read/write token for
DATABASE_NAME
"

Copy the raw token string immediately and store it securely. It’s shown only once.

List tokens

List token names, types, and expirations (token strings aren’t shown):

influxdb3 show tokens

Delete a token

influxdb3 delete token --token-name "
TOKEN_NAME
"

Because InfluxDB 3 Cloud runs the same InfluxDB 3 engine as InfluxDB 3 Enterprise, token management works the same way. For more details, see Manage tokens in InfluxDB 3 Enterprise.


Was this page helpful?

Thank you for your feedback!


InfluxDB OSS 2.9.0: API tokens are hashed by default

Stronger token security in InfluxDB OSS 2.9.0 — tokens are hashed on disk by default. Existing tokens are hashed on first startup and can’t be recovered afterward. Capture any plaintext tokens you still need before you upgrade.

View InfluxDB OSS 2.9.0 release notes

Hashed tokens authenticate exactly like unhashed tokens — clients and integrations keep working.

Also new in 2.9.0:

  • Configurable backup compression
  • Restore support for backups containing hashed tokens
  • Tighter Edge Data Replication queue validation
  • Flux upgrade
  • Compaction reliability improvements

Key enhancements in Explorer 1.9

Explorer 1.9 is now available with InfluxQL support, an AI-assisted Flux to SQL converter (beta), and new live sample data simulators.

View Explorer 1.9 release notes

Explorer 1.9 includes new features and improvements that make it easier to query, visualize, and manage data.

Highlights:

  • Flux to SQL converter (beta): Convert Flux queries to SQL with an AI-assisted converter.
  • InfluxQL support: Query data with InfluxQL in the Data Explorer and dashboards, and save and load InfluxQL queries.
  • InfluxQL visualizations: Render line and bar charts from InfluxQL results with per-tag series grouping.
  • Query error history: Review a history of query errors in the query tool.
  • Live sample data simulators: Generate continuous live sample data with new bird data and signal generator simulators.

For more details, see Explorer 1.9 release notes

InfluxDB 3.10 is now available

InfluxDB 3 Core 3.10 adds an automatic catalog format upgrade, a configurable query-concurrency limit, and processing engine improvements.

Key updates in InfluxDB 3 Core 3.10:

  • Catalog format upgrade: the on-disk catalog automatically upgrades from format v2 to v3 on first 3.10 startup. Migration is one-way—back up your catalog before upgrading.
  • --max-concurrent-queries: limit concurrent queries (adjustable at runtime).
  • GET /ready endpoint for readiness probes.
  • Processing engine: cross-database queries and trigger lockdown flags.

For more information, see the InfluxDB 3 Core release notes.

InfluxDB 3.10 is now available

InfluxDB 3 Enterprise 3.10 adds automated backup and restore, row-level deletions, and user management, with an automatic catalog format upgrade and performance preview improvements.

Key updates in InfluxDB 3 Enterprise 3.10:

  • Catalog format upgrade: the on-disk catalog automatically upgrades from format v2 to v3 on first 3.10 startup. Migration is one-way—back up your catalog before upgrading.
  • Automated backup and restore (beta)
  • Row-level deletions
  • User management (authentication and RBAC) — preview
  • Performance preview improvements

Backup and restore, row-level deletions, and the performance preview require the Enterprise storage engine upgrade (opt-in beta). Beta and preview features are subject to breaking changes and aren’t recommended for production use.

For more information, see the InfluxDB 3 Enterprise release notes

Telegraf Enterprise is now generally available

Telegraf Enterprise is now generally available, along with Telegraf Controller v1.0.

Telegraf Enterprise combines Telegraf Controller, a centralized management console for Telegraf, with official support from InfluxData. Manage configurations, monitor fleet health, and operate tens of thousands of Telegraf agents from a single system.

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On September 15, 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