Documentation

Use API tokens

API tokens authenticate requests to Telegraf Controller. Use tokens to connect Telegraf agents, authorize heartbeat reporting, and integrate external API clients.

With Telegraf agents

Configure your Telegraf agent to include an API token when retrieving configurations and reporting heartbeats to Telegraf Controller.

Telegraf agents require API tokens with the following permissions:

  • Configs: Read
  • Heartbeat: Write

Use the TELEGRAF_CONTROLLER_TOKEN environment variable

When retrieving a configuration from a URL, Telegraf only sends an Authorization header when it detects an authentication environment variable. To authorize Telegraf to retrieve a configuration from Telegraf Controller, define the TELEGRAF_CONTROLLER_TOKEN environment variable before starting Telegraf:

export TELEGRAF_CONTROLLER_TOKEN=
YOUR_TC_API_TOKEN
telegraf \ --config "http://telegraf_controller.example.com/api/configs/xxxxxx/toml"

Replace YOUR_TC_API_TOKEN with your Telegraf Controller API token.

When TELEGRAF_CONTROLLER_TOKEN is set, Telegraf sends the token in the Authorization header using the Bearer scheme. The Telegraf config watcher (enabled with --config-url-watch-interval) uses the same environment variable to authorize its periodic update checks.

Using Telegraf 1.38.x or earlier?

Telegraf 1.39+ is required to read TELEGRAF_CONTROLLER_TOKEN. On earlier versions, use the INFLUX_TOKEN environment variable instead. Telegraf sends INFLUX_TOKEN in the Authorization header using the Token scheme. Telegraf Controller accepts tokens sent with either scheme, so you can upgrade Telegraf at your own pace.

If both environment variables are set on Telegraf 1.39+, TELEGRAF_CONTROLLER_TOKEN takes precedence.

For heartbeat requests

Telegraf uses the Heartbeat output plugin to send heartbeats to Telegraf Controller. Use the TELEGRAF_CONTROLLER_TOKEN environment variable to define the token option in your heartbeat plugin configuration. Telegraf uses the environment variable value defined when starting Telegraf.

[[outputs.heartbeat]]
  url = "http://telegraf_controller.example.com/agents/heartbeat"
  instance_id = "&{agent_id}"
  interval = "1m"
  include = ["hostname", "statistics", "configs"]
  token = "${TELEGRAF_CONTROLLER_TOKEN}"

When authentication is required for the heartbeat endpoint, agents must include a valid token with each heartbeat request. If a heartbeat request is missing a token or includes an invalid token, Telegraf Controller rejects the request and the agent’s status is not updated.

With external API clients

Include the token in the Authorization header when making API requests to Telegraf Controller:

Authorization: Bearer tc-apiv1_<token>

The token’s permissions determine which API endpoints and operations are accessible. Requests made with a token that lacks the required permissions are rejected with an authorization error.

For more information about using the API, including how to explore the interactive API reference, see the Telegraf Controller API.

If authentication is disabled for an endpoint, requests to those endpoints do not require a token. See Endpoint authentication for details on configuring authentication requirements per endpoint.


Was this page helpful?

Thank you for your feedback!


InfluxDB OSS 2.9.0: API tokens are hashed by default

Stronger token security in InfluxDB OSS 2.9.0 — tokens are hashed on disk by default. Existing tokens are hashed on first startup and can’t be recovered afterward. Capture any plaintext tokens you still need before you upgrade.

View InfluxDB OSS 2.9.0 release notes

Hashed tokens authenticate exactly like unhashed tokens — clients and integrations keep working.

Also new in 2.9.0:

  • Configurable backup compression
  • Restore support for backups containing hashed tokens
  • Tighter Edge Data Replication queue validation
  • Flux upgrade
  • Compaction reliability improvements

Key enhancements in Explorer 1.9

Explorer 1.9 is now available with InfluxQL support, an AI-assisted Flux to SQL converter (beta), and new live sample data simulators.

View Explorer 1.9 release notes

Explorer 1.9 includes new features and improvements that make it easier to query, visualize, and manage data.

Highlights:

  • Flux to SQL converter (beta): Convert Flux queries to SQL with an AI-assisted converter.
  • InfluxQL support: Query data with InfluxQL in the Data Explorer and dashboards, and save and load InfluxQL queries.
  • InfluxQL visualizations: Render line and bar charts from InfluxQL results with per-tag series grouping.
  • Query error history: Review a history of query errors in the query tool.
  • Live sample data simulators: Generate continuous live sample data with new bird data and signal generator simulators.

For more details, see Explorer 1.9 release notes

InfluxDB 3.10 is now available

InfluxDB 3 Core 3.10 adds an automatic catalog format upgrade, a configurable query-concurrency limit, and processing engine improvements.

Key updates in InfluxDB 3 Core 3.10:

  • Catalog format upgrade: the on-disk catalog automatically upgrades from format v2 to v3 on first 3.10 startup. Migration is one-way—back up your catalog before upgrading.
  • --max-concurrent-queries: limit concurrent queries (adjustable at runtime).
  • GET /ready endpoint for readiness probes.
  • Processing engine: cross-database queries and trigger lockdown flags.

For more information, see the InfluxDB 3 Core release notes.

InfluxDB 3.10 is now available

InfluxDB 3 Enterprise 3.10 adds automated backup and restore, row-level deletions, and user management, with an automatic catalog format upgrade and performance preview improvements.

Key updates in InfluxDB 3 Enterprise 3.10:

  • Catalog format upgrade: the on-disk catalog automatically upgrades from format v2 to v3 on first 3.10 startup. Migration is one-way—back up your catalog before upgrading.
  • Automated backup and restore (beta)
  • Row-level deletions
  • User management (authentication and RBAC) — preview
  • Performance preview improvements

Backup and restore, row-level deletions, and the performance preview require the Enterprise storage engine upgrade (opt-in beta). Beta and preview features are subject to breaking changes and aren’t recommended for production use.

For more information, see the InfluxDB 3 Enterprise release notes

Telegraf Enterprise is now generally available

Telegraf Enterprise is now generally available, along with Telegraf Controller v1.0.

Telegraf Enterprise combines Telegraf Controller, a centralized management console for Telegraf, with official support from InfluxData. Manage configurations, monitor fleet health, and operate tens of thousands of Telegraf agents from a single system.

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On September 15, 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