Documentation

InfluxDB Clustered

Revoke a management token

Use the influxctl management revoke command to revoke a management token and remove all access associated with the token.

  1. If you haven’t already, download and install the influxctl CLI.

  2. Run the influxctl management list command to output tokens with their IDs. Copy the ID of the token you want to delete.

    influxctl management list

  3. Run the influxctl management revoke command and provide the following:

    • Optional: --force flag to skip command confirmation
    • Token ID to delete

  4. Confirm that you want to delete the token.

influxctl management revoke --force 
TOKEN_ID

Replace TOKEN_ID with the ID of the token you want to revoke.

Revoked tokens are included when listing management tokens

Revoked tokens still appear when listing management tokens, but they are no longer valid for any operations.

Was this page helpful?

Thank you for your feedback!

© 2025 InfluxData, Inc.

What is your InfluxDB cluster URL?

Enter your InfluxDB cluster URL and we’ll update code examples for you.

Enter cluster URL

Thank you for your feedback!

Let us know what we can do better:

Thank you!

No thanks

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 February 3, 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