Documentation

InfluxDB 3 Core

List databases

Use the influxdb3 show databases command, the /api/v3/configure/database HTTP API endpoint, or InfluxDB 3 Explorer to list databases in InfluxDB 3 Core.

List databases using the influxdb3 CLI

Provide the following:

influxdb3 show databases

Output formats

The influxdb3 show databases command supports output formats:

Use the --format flag to specify the output format:

influxdb3 show databases --format json

Example output

View example pretty-formatted output

View example JSON-formatted output

View example JSON-line-formatted output

View example CSV-formatted output

Output 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 databases \
  --format parquet \
  --output databases.parquet

Alternatively, use the influxdb3 query command to query system tables:

influxdb3 query \
  --database _internal \
  --format parquet \
  --output databases.parquet \
  "SELECT * FROM system.databases"

List deleted databases

To list deleted databases, include the --show-deleted option with your influxdb3 show databases command:

influxdb3 show databases --show-deleted

List databases using the HTTP API

To list databases using the HTTP API, send a GET request to the /api/v3/configure/database endpoint.

GET localhost:8181/api/v3/configure/database?format=pretty

Include the format query parameter and specify one of the following formats:

  • pretty
  • json
  • jsonl
  • csv
  • parquet

Pretty output JSON output Parquet output

Include the following in your request:

  • Headers:

    • Authorization: Bearer with your token

  • Query Parameters:

    • format=pretty
curl --request GET "localhost:8181/api/v3/configure/database?format=pretty" \
  --header "Authorization: Bearer 
AUTH_TOKEN
"

The response body contains a table of database names:

+---------------------+
| iox::database       |
+---------------------+
| _internal           |
| home                |
| home_actions        |
| noaa                |
+---------------------+

Include the following in your request:

  • Headers:

    • Authorization: Bearer with your token

  • Query Parameters:

    • format=json
curl --request GET "localhost:8181/api/v3/configure/database?format=json" \
  --header "Authorization: Bearer 
AUTH_TOKEN
"

The response body contains a JSON array of database objects whose keys are iox::database:

[
  {
    "iox::database": "home"
  },
  {
    "iox::database": "home_actions"
  },
  {
    "iox::database": "noaa"
  }
]

Include the following in your request:

  • Headers:

    • Authorization: Bearer with your token

  • Query Parameters:

    • format=parquet

  • An output destination for the Parquet file

curl "localhost:8181/api/v3/configure/database?format=parquet" \
  -o databases.parquet \
  --header "Authorization: Bearer 
AUTH_TOKEN
"

For Parquet responses, you must provide an output destination because the format is binary.

The response contains the databases list.

A successful request returns HTTP status 200.

List databases using InfluxDB 3 Explorer

You can also view all databases using the InfluxDB 3 Explorer web interface:

  1. If you haven’t already, see how to get started with Explorer and connect to your InfluxDB 3 Core server.
  2. In Explorer, click Databases in the left navigation.
  3. The Databases page displays a list of all databases with the following information:
    • Database name
    • Retention period (if configured)
    • Number of tables in the database
    • Creation date

For more information, see Manage databases with InfluxDB 3 Explorer.

Was this page helpful?

Thank you for your feedback!

© 2026 InfluxData, Inc.

What is your InfluxDB 3 Core URL?

Customize your InfluxDB 3 Core URL and we’ll update code examples for you.

Default
Custom

For more information, see InfluxDB Cloud regions or InfluxDB OSS URLs.

Thank you for your feedback!

Let us know what we can do better:

Thank you!

No thanks

Select a new date

Select a date in your database's retention period.

Update

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