Documentation

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 \
  --token 
API_TOKEN
\
--id
AUTHORIZATION_ID

Delete a token using the InfluxDB API

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

DELETE https://cloud2.influxdata.com/api/v2/authorizations/{AUTH_ID}

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 \
  https://cloud2.influxdata.com/api/v2/authorizations?user=user2 \
  --header "Authorization: Token 
API_TOKEN
"
\
--header 'Content-type: application/json' \ | jq .authorizations[0].id \ | xargs -I authid curl --request DELETE \ https://cloud2.influxdata.com/api/v2/authorizations/authid \ --header "Authorization: Token
API_TOKEN
"
\
--header 'Content-type: application/json'

Was this page helpful?

Thank you for your feedback!


InfluxDB 3.9: Performance upgrade preview

InfluxDB 3 Enterprise 3.9 includes a beta of major performance upgrades with faster single-series queries, wide-and-sparse table support, and more.

InfluxDB 3 Enterprise 3.9 includes a beta of major performance and feature updates.

Key improvements:

  • Faster single-series queries
  • Consistent resource usage
  • Wide-and-sparse table support
  • Automatic distinct value caches for reduced latency with metadata queries

Preview features are subject to breaking changes.

For more information, see:

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:

Telegraf Controller v0.0.6-beta now available

Telegraf Controller v0.0.6-beta is now available with new features, improvements, and bug fixes.

View the release notes
Download Telegraf Controller v0.0.6-beta

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

InfluxDB Cloud Serverless