Documentation

influxctl token delete

The influxctl token delete command deletes a database token from an InfluxDB Cloud Dedicated cluster and revokes all permissions associated with the token.

Usage

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

Deleting a token is immediate and cannot be undone

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

Rotate deleted tokens

After deleting a database token, any clients using the deleted token need to be updated with a new database token to continue to interact with your InfluxDB Cloud Dedicated cluster.

Arguments

ArgumentDescription
TOKEN_IDDatabase token ID to delete

Flags

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

Examples

In the examples below, replace the following:

  • TOKEN_ID: token ID to delete

Delete a database token

influxctl token delete 
TOKEN_ID

Delete multiple database tokens

influxctl token delete 
TOKEN_ID_1
TOKEN_ID_2

Was this page helpful?

Thank you for your feedback!


Introducing InfluxDB Clustered

A highly available InfluxDB 3.0 cluster on your own infrastructure.

InfluxDB Clustered is a highly available InfluxDB 3.0 cluster built for high write and query workloads on your own infrastructure.

InfluxDB Clustered is currently in limited availability and is only available to a limited group of InfluxData customers. If interested in being part of the limited access group, please contact the InfluxData Sales team.

Learn more
Contact InfluxData Sales

The future of Flux

Flux is going into maintenance mode. You can continue using it as you currently are without any changes to your code.

Flux is going into maintenance mode and will not be supported in InfluxDB 3.0. This was a decision based on the broad demand for SQL and the continued growth and adoption of InfluxQL. We are continuing to support Flux for users in 1.x and 2.x so you can continue using it with no changes to your code. If you are interested in transitioning to InfluxDB 3.0 and want to future-proof your code, we suggest using InfluxQL.

For information about the future of Flux, see the following: