Documentation

influxctl token revoke

The influxctl token revoke command revokes a database token associated with an InfluxDB cluster and removes all permissions associated with the token.

Usage

influxctl token revoke <TOKEN_ID> [<TOKEN_ID_N>...]

Revoking a token is immediate and cannot be undone

Revoking a database token is a destructive action that takes place immediately and cannot be undone.

Rotate revoked tokens

After revoking a database token, any clients using the revoked token need to be updated with a new database token to continue to interact with your InfluxDB cluster.

Aliases

delete

Arguments

ArgumentDescription
TOKEN_IDDatabase token ID to revoke

Flags

FlagDescription
--forceDo not prompt for confirmation to revoke (default is false)
-h--helpOutput command help

Examples

In the examples below, replace the following:

  • TOKEN_ID: token ID to revoke

Revoke a database token

influxctl token revoke 
TOKEN_ID

Revoke multiple database tokens

influxctl token revoke 
TOKEN_ID_1
TOKEN_ID_2

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