Documentation

influxdb3 show tokens

The influxdb3 show tokens command lists authentication tokens in your InfluxDB 3 Enterprise server.

Usage

influxdb3 show tokens [OPTIONS]

Options

OptionDescription
-H--hostHost URL of the running InfluxDB 3 Enterprise server (default is http://127.0.0.1:8181)
--token(Required) Authentication token
--formatOutput format (pretty (default), json, jsonl, csv, or parquet)
--outputPath where to save output when using the parquet format
--tls-caPath to a custom TLS certificate authority (for testing or self-signed certificates)
-h--helpPrint help information
--help-allPrint detailed help information

Option environment variables

You can use the following environment variables to set command options:

Environment VariableOption
INFLUXDB3_HOST_URL--host
INFLUXDB3_AUTH_TOKEN--token

Examples

List all tokens

influxdb3 show tokens

List tokens in different output formats

You can specify the output format using the --format option:

# JSON format
influxdb3 show tokens --format json

# JSON Lines format
influxdb3 show tokens --format jsonl

# CSV format
influxdb3 show tokens --format csv

Output tokens to a Parquet file

Parquet is a binary format. Use the --output option to specify the file where you want to save the Parquet data.

influxdb3 show tokens \
  --format parquet \
  --output /Users/me/tokens.parquet

Was this page helpful?

Thank you for your feedback!


New in InfluxDB 3.7

Key enhancements in InfluxDB 3.7 and the InfluxDB 3 Explorer 1.5.

See the Blog Post

InfluxDB 3.7 is now available for both Core and Enterprise, landing alongside version 1.5 of the InfluxDB 3 Explorer UI. This release focuses on giving developers faster visibility into what their system is doing with one-click monitoring, a streamlined installation pathway, and broader updates that simplify day-to-day operations.

For more information, check out:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On February 3, 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