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!


Telegraf Enterprise now in public beta

Get early access to the Telegraf Controller and provide feedback to help shape the future of Telegraf Enterprise.

See the Blog Post

The upcoming Telegraf Enterprise offering is for organizations running Telegraf at scale and is comprised of two key components:

  • Telegraf Controller: A control plane (UI + API) that centralizes Telegraf configuration management and agent health visibility.
  • Telegraf Enterprise Support: Official support for Telegraf Controller and Telegraf plugins.

Join the Telegraf Enterprise beta to get early access to the Telegraf Controller and provide feedback to help shape the future of Telegraf Enterprise.

For more information:

New in InfluxDB 3.8

Key enhancements in InfluxDB 3.8 and the InfluxDB 3 Explorer 1.6.

See the Blog Post

InfluxDB 3.8 is now available for both Core and Enterprise, alongside the 1.6 release of the InfluxDB 3 Explorer UI. This release is focused on operational maturity and making InfluxDB easier to deploy, manage, and run reliably in production.

For more information, check out:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On May 27, 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