Documentation

influxdb3 delete token

The influxdb3 delete token command deletes an authorization token from the InfluxDB 3 Enterprise server.

Usage

# Syntax
influxdb3 delete token [OPTIONS]

Options

OptionDescriptionDefaultEnvironment
--token(Required) The token for authentication with the InfluxDB 3 Enterprise serverINFLUXDB3_AUTH_TOKEN
--token-name(Required) The name of the token to be deleted
--tls-caPath to a custom TLS certificate authority (for self-signed or internal certificates)INFLUXDB3_TLS_CA
--tls-no-verifyDisable TLS certificate verification (Not recommended in production, useful for self-signed certificates)INFLUXDB3_TLS_NO_VERIFY
-h, --helpPrint help information
--help-allPrint detailed help information

Examples

In the examples below, replace the following:

  • AUTH_TOKEN: Authentication token with permission to delete tokens
  • TOKEN_TO_DELETE: Name of the token to delete

Delete a token by name

influxdb3 delete token --token-name 
TOKEN_TO_DELETE
--token
AUTH_TOKEN

Show help for the command

influxdb3 delete token --help

Was this page helpful?

Thank you for your feedback!


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:

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