Documentation

List admin tokens

Use the influxdb3 CLI or the /api/v3 HTTP API to list admin tokens for your InfluxDB 3 Core instance.

Admin tokens have permissions=*:*:*, which allows access to all data and resources in your InfluxDB 3 instance.

Token metadata includes the hashed token string. InfluxDB 3 does not store the raw token string.

Required permissions

Listing admin tokens requires a valid InfluxDB admin token. For more information, see how to provide your token.

List all tokens

The influxdb3 show tokens CLI command lists all admin and resource tokens in your InfluxDB 3 instance.

influxdb3 show tokens

Query token metadata

To filter tokens and retrieve specific details using SQL, query the system.tokens table in the _internal system database–for example:

Filter for admin tokens

influxdb3 query \
  --database _internal \
  --format csv \
  "SELECT name, permissions FROM system.tokens WHERE permissions = '*:*:*'"
curl -G \
  "http://localhost:8181/api/v3/query_sql" \
  --data-urlencode "db=_internal" \
  --data-urlencode "q=SELECT name, permissions FROM system.tokens WHERE permissions = '*:*:*'" \
  --data-urlencode "format=csv" \
  --header 'Accept: text/csv' \
  --header "Authorization: Bearer 
AUTH_TOKEN
"

Filter by date

influxdb3 query \
  --db _internal \
  "SELECT name, permissions FROM system.tokens WHERE created_at > '2025-01-01 00:00:00'"
curl -G \
"http://localhost:8181/api/v3/query_sql" \
--data-urlencode "db=_internal" \
--data-urlencode "q=SELECT name, permissions FROM system.tokens WHERE created_at > '2025-01-01 00:00:00'" \
--header "Accept: application/json" \
--header "Authorization: Bearer 
AUTH_TOKEN
"

Output formats

Use the format option to specify the output format for commands.

InfluxDB 3 Core commands used in this guide support the following output formats:

  • json (default for HTTP API)
  • pretty (default for CLI)
  • jsonl
  • csv
  • parquet (output to a file)
influxdb3 show tokens \
  --format jsonl
curl -G \
  "http://localhost:8181/api/v3/query_sql" \
  --data-urlencode "db=_internal" \
  --data-urlencode "q=SELECT * FROM system.tokens" \
  --data-urlencode "format=csv" \
  --header 'Accept: text/csv' \
  --header "Authorization: Bearer 
AUTH_TOKEN
"

Output to a Parquet file

Parquet is a binary format.

To output to a Parquet file using the CLI, include the --output option with a destination path for the file.

To output a Parquet file using the HTTP API, your client must be able to handle binary data–for example, using cURL’s --output option.

influxdb3 show tokens \
  --format parquet \
  --output 
/PATH/TO/FILE.parquet
curl -G \
"http://localhost:8181/api/v3/query_sql" \
--data-urlencode "db=_internal" \
--data-urlencode "q=SELECT * FROM system.tokens" \
--data-urlencode "format=parquet" \
--header "Accept: application/parquet" \
--header "Authorization: Bearer 
AUTH_TOKEN
"
\
--output
/PATH/TO/FILE.parquet

Replace /PATH/TO/FILE.parquet with the path to the file where you want to save the Parquet data.

Filter the token list

Use command-line tools such as grep or jq to filter the output of the influxdb3 show tokens command or the HTTP API response–for example:

influxdb3 show tokens --format pretty |
grep _admin
curl -G \
  "http://localhost:8181/api/v3/query_sql" \
  --data-urlencode "db=_internal" \
  --data-urlencode "q=SELECT * FROM system.tokens" \
  --data-urlencode "format=pretty" \
  --header "Accept: application/json" \
  --header "Authorization: Bearer 
AUTH_TOKEN
"
|
grep _admin
influxdb3 show tokens --format json |
jq '.[] | {name: .name, permissions: .permissions}'
curl -G \
  "http://localhost:8181/api/v3/query_sql" \
  --data-urlencode "db=_internal" \
  --data-urlencode "q=SELECT name, created_at FROM system.tokens WHERE permissions = '*:*:*' AND created_at > '2025-01-01 00:00:00'" \
  --data-urlencode "format=json" \
  --header "Accept: application/json" \
  --header "Authorization: Bearer 
AUTH_TOKEN
"
|
jq '.[] | {name: .name, created_at: .created_at}'

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