Documentation

Delete secrets

This page documents an earlier version of InfluxDB OSS. InfluxDB 3 Core is the latest stable version.

Delete secrets using the influx command line interface (CLI) or the InfluxDB API.

Delete a secret using the influx CLI

Use the influx secret delete command to delete a secret key-value pair from your organization. Provide the secret key to delete with the -k or --key flag.

# Syntax
influx secret delete -k <secret-key>

# Example
influx secret delete -k foo

Delete secrets using the InfluxDB API

Use the POST request method and the orgs/{orgID}/secrets/delete API endpoint to delete one or more secrets.

Include the following:

  • Your organization ID in the request URL
  • Your API token in the Authorization header
  • An array of secret keys to delete in the request body
curl --request GET http://localhost:8086/api/v2/orgs/<org-id>/secrets/delete \
  --header 'Authorization: Token YOURAUTHTOKEN' \
  --data '{
  "secrets": [
    "<secret-key>"
  ]
}'

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