Documentation

Delete a table

Use the influxdb3 delete table command or the HTTP API to delete a table from a specified database in InfluxDB 3 Core.

With InfluxDB 3 Core, tables and measurements are synonymous. By default, InfluxDB 3 Core performs a soft delete, which schedules the table for deletion and makes it unavailable for querying. You can also schedule a hard deletion to permanently remove the table and its data.

Deleting a table cannot be undone

Deleting a table is a destructive action. Once a table is deleted, data stored in that table cannot be recovered.

Delete a table using the influxdb3 CLI

Use the influxdb3 delete table command to delete a table:

influxdb3 delete table \
  --database 
DATABASE_NAME
\
--token
AUTH_TOKEN
\
TABLE_NAME

Replace the following:

  • DATABASE_NAME: the name of the database containing the table
  • TABLE_NAME: the name of the table to delete
  • AUTH_TOKEN: your admin token

Hard delete a table immediately

To permanently delete a table and its data immediately, use the --hard-delete now flag:

influxdb3 delete table \
  --database 
DATABASE_NAME
\
--token
AUTH_TOKEN
\
--hard-delete now \
TABLE_NAME

Schedule a hard deletion

To schedule a table for hard deletion at a specific time, use the --hard-delete flag with a timestamp:

influxdb3 delete table \
  --database 
DATABASE_NAME
\
--token
AUTH_TOKEN
\
--hard-delete "2025-12-31T23:59:59Z" \
TABLE_NAME

Delete a table using the HTTP API

To delete a table using the HTTP API, send a DELETE request to the /api/v3/configure/table endpoint:

DELETE localhost:8181/api/v3/configure/table

Include the following in your request:

  • Query parameters:
    • db: Database name
    • table: Table name to delete
    • hard_delete_at: (Optional) Timestamp for hard deletion
  • Headers:
    • Authorization: Bearer with your authentication token

Soft delete a table

curl -X DELETE "localhost:8181/api/v3/configure/table?db=
DATABASE_NAME
&table=
TABLE_NAME
"
\
--header "Authorization: Bearer
AUTH_TOKEN
"

Replace the following:

  • DATABASE_NAME: the name of the database containing the table
  • TABLE_NAME: the name of the table to delete
  • AUTH_TOKEN: your admin token

Schedule a hard deletion

To schedule a hard deletion at a specific time, include the hard_delete_at parameter with an ISO 8601 timestamp:

curl -X DELETE "localhost:8181/api/v3/configure/table?db=
DATABASE_NAME
&table=
TABLE_NAME
&hard_delete_at=2025-12-31T23:59:59Z"
\
--header "Authorization: Bearer
AUTH_TOKEN
"

Response

A successful deletion returns HTTP status 200 with no content body.

Example error response

If the table doesn’t exist, the API returns HTTP status 404:

{
  "error": "Table not found"
}

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