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!


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