Documentation

Update a token

Update an API token’s description and status using the InfluxDB user interface (UI), influx CLI, or InfluxDB API.

Update a token in the InfluxDB UI

To update tokens in the InfluxDB UI, navigate to the API Tokens management page. In the navigation menu on the left, select Load Data > API Tokens.

Update a token’s description

  1. On the token management page, click the pencil icon () next to the token’s description.
  2. Update the token description, and then click anywhere else to save.

Enable or disable a token in the InfluxDB UI

  1. On the token management page, find the token that you would like to enable or disable.
  2. Click the token description.
  3. Click the Active toggle.

Enable a token using the influx CLI

Use the influx auth active command to activate a token.

Provide the following flags:

  • --token: API token with permission to update authorizations
  • --id: Authorization ID to enable (available in the output of influx auth list)
influx auth active \
  --token 
API_TOKEN
\
--id
AUTHORIZATION_ID

Disable a token using the influx CLI

Use the influx auth inactive command to deactivate a token.

Provide the following flags:

  • --token: API token with permission to update authorizations
  • --id: Authorization ID to disable (available in the output of influx auth list)
influx auth inactive \
  --token 
API_TOKEN
\
--id
AUTHORIZATION_ID

Update a token using the InfluxDB API

Use the /api/v2/authorizations InfluxDB API endpoint to update the description and status of a token.

PATCH 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 update
  • Request body: JSON object with authorization properties to update

Disable a token

# Update the description and status of 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 PATCH \ https://cloud2.influxdata.com/api/v2/authorizations/authid \ --header "Authorization: Token
API_TOKEN
"
\
--header 'Content-type: application/json' \ --data '{ "description": "deactivated_auth", "status": "inactive" }' | jq .

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

InfluxDB Cloud Serverless