---
title: List admin tokens
description: Use the influxdb3 CLI or the /api/v3 HTTP API to list admin tokens for your InfluxDB 3 Enterprise instance. Use the influxdb3 show tokens command to list all tokens or use SQL to query token metadata directly from the system.tokens table.
url: https://docs.influxdata.com/influxdb3/enterprise/admin/tokens/admin/list/
estimated_tokens: 1238
product: InfluxDB 3 Enterprise
version: enterprise
publisher: InfluxData
canonical: https://docs.influxdata.com/influxdb3/enterprise/admin/tokens/admin/list/
date: '2025-04-28T10:29:16-05:00'
lastmod: '2025-04-28T10:29:16-05:00'
---

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

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

> [!Note]
> 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](/influxdb3/enterprise/admin/tokens/)or a token with read access to the `_internal` system database
.
For more information, see how to [provide your token](/influxdb3/enterprise/admin/tokens/#provide-your-token).

## List all tokens

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

```bash
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

[CLI](#cli-query-tokens)[HTTP API](#http-api-query-tokens)

```bash
influxdb3 query \
  --database _internal \
  --format csv \
  "SELECT name, permissions FROM system.tokens WHERE permissions = '*:*:*'"
```

```bash
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

[CLI](#cli-filter-in-query)[HTTP API](#http-api-filter-in-query)

```bash
influxdb3 query \
  --db _internal \
  "SELECT name, permissions FROM system.tokens WHERE created_at > '2025-01-01 00:00:00'"
```

```bash
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 Enterprise 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](#output-to-a-parquet-file))*

[CLI](#format-using-the-cli)[HTTP API](#format-using-the-api)

```bash
influxdb3 show tokens \
  --format jsonl
```

```bash
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](https://parquet.apache.org/) 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.

[CLI](#cli-output-to-parquet)[HTTP API](#http-api-output-to-parquet)

```bash
influxdb3 show tokens \
  --format parquet \
  --output /PATH/TO/FILE.parquet
```

```bash
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:

[CLI](#cli-filter-admin-using-grep)[HTTP API](#http-api-filter-admin-using-grep)

```bash
influxdb3 show tokens --format pretty |
grep _admin
```

```bash
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
```

[CLI](#cli-filter-output-using-jq)[HTTP API](#http-api-filter-output-using-jq)

```bash
influxdb3 show tokens --format json |
jq '.[] | {name: .name, permissions: .permissions}'
```

```bash
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}'
```

#### Related

* [Manage tokens with InfluxDB 3 Explorer](/influxdb3/explorer/manage-tokens/)