Documentation

Revoke a database token

Use the influxctl CLI or the Management HTTP API to revoke a database token associated with your InfluxDB Cloud Dedicated cluster.

The InfluxDB Cloud Dedicated administrative UI includes a portal for creating and managing database tokens.

Administrators can use this portal to:

  • View token details
  • Add read and write permissions for specific databases to a token
  • Edit a token’s existing read and write permissions for a database
  • Create a database token
  • Revoke a database token
  1. To access the InfluxDB Cloud Dedicated Admin UI, visit the following URL in your browser:

    https://cluster-id.a.influxdb.io
    
  2. Use the credentials provided by InfluxData to log into the Admin UI. If you don’t have login credentials, contact InfluxData support.

  3. After you log in, the Account Management portal displays account information and the list of clusters associated with your account.

  4. Click the row for the cluster that contains the database you want to manage tokens for. You can Search clusters by name or ID to filter the list and use the sort button and column headers to sort the list.

  5. Click the Database Tokens button in the upper right corner of the Cluster screen.

  6. The Database Tokens portal displays the list of database tokens associated with the cluster. Use the sort and filter options above the list to find a specific token.

  7. Click the Options button (three vertical dots) to the right of the token you want to revoke.

  8. In the options menu, click Revoke Token. The Revoke Database Token dialog displays.

    Revoke database token dialog
  9. Check the box to confirm that you understand the risk.

  10. Click the Revoke Token button. The token is revoked and filtered from the list of active tokens.

Use the influxctl token revoke command to revoke a database token and remove all permissions associated with the token.

  1. If you haven’t already, download and install the influxctl CLI, and then configure an influxctl connection profile for your cluster.

  2. To list token IDs, run the influxctl token list command in your terminal.

    influxctl token list

    Copy the token ID of the token you want to revoke.

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

    • Token ID to revoke
  4. Confirm that you want to revoke the token.

influxctl token revoke 
TOKEN_ID

This example uses cURL to send a Management HTTP API request, but you can use any HTTP client.

  1. If you haven’t already, follow the instructions to install cURL for your system.

  2. In your terminal, use cURL to send a request to the following InfluxDB Cloud Dedicated endpoint:

    DELETE https://console.influxdata.com/api/v0/accounts/ACCOUNT_ID/clusters/CLUSTER_ID/tokens/TOKEN_ID

    In the URL, provide the following:

    Provide the following request headers:

    Specify the DELETE request method.

The following example shows how to use the Management API to revoke a database token and remove all permissions associated with the token:

curl \
 --location "https://console.influxdata.com/api/v0/accounts/
ACCOUNT_ID
/clusters/
CLUSTER_ID
/tokens/
TOKEN_ID
"
\
--request DELETE \ --header "Accept: application/json" \ --header "Authorization: Bearer $
MANAGEMENT_TOKEN
" \

Replace the following:

  • ACCOUNT_ID: the ID of the InfluxDB Cloud Dedicated account associated with the token you want to revoke
  • CLUSTER_ID: the ID of the InfluxDB Cloud Dedicated cluster associated with the token you want to revoke
  • MANAGEMENT TOKEN: a management token for your InfluxDB Cloud Dedicated cluster
  • TOKEN_ID: the ID of the database token to revoke

Revoking a token is immediate and cannot be undone

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

Rotate revoked tokens

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


Was this page helpful?

Thank you for your feedback!


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 November 3, 2025, 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