Delete a token

Delete API tokens using the InfluxDB user interface (UI), influx command line interface (CLI), or InfluxDB API. Once deleted, all users and external integrations using the API token will no longer have access to your InfluxDB instance.

Delete tokens in the InfluxDB UI

  1. In the navigation menu on the left, select Load Data > API Tokens.

  2. Find the token that you would like to delete.

  3. Click the icon located far right of the token description.

  4. Click Confirm to delete the token.

Delete a token using the influx CLI

Use the influx auth delete command to delete a token.

Provide the following flags:

  • --token: API token with permission to delete authorizations
  • --id: Authorization ID to delete (available in the output of influx auth find)
influx auth delete \

Delete a token using the InfluxDB API

Use the /api/v2/authorizations InfluxDB API endpoint to delete a token.


Include the following in your request:

  • Headers:
    • Authorization: Token API_TOKEN (API token with the write: authorizations permission)
    • Content-type: application/json
  • Path parameters:
    • authID: Authorization ID to delete
# Delete the first authorization listed for the user.
curl --request GET \ \
  --header "Authorization: Token 
--header 'Content-type: application/json' \ | jq .authorizations[0].id \ | xargs -I authid curl --request DELETE \ \ --header "Authorization: Token
--header 'Content-type: application/json'

Was this page helpful?

Thank you for your feedback!

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:

InfluxDB Cloud Serverless