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!


New in InfluxDB 3.5

Key enhancements in InfluxDB 3.5 and the InfluxDB 3 Explorer 1.3.

See the Blog Post

InfluxDB 3.5 is now available for both Core and Enterprise, introducing custom plugin repository support, enhanced operational visibility with queryable CLI parameters and manual node management, stronger security controls, and general performance improvements.

InfluxDB 3 Explorer 1.3 brings powerful new capabilities including Dashboards (beta) for saving and organizing your favorite queries, and cache querying for instant access to Last Value and Distinct Value caches—making Explorer a more comprehensive workspace for time series monitoring and analysis.

For more information, check out:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On November 3, 2025, 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