Documentation

Delete data

This page documents an earlier version of InfluxDB OSS. InfluxDB 3 Core is the latest stable version.

Use the influx CLI or the InfluxDB API /api/v2/delete endpoint to delete data from an InfluxDB bucket.

InfluxDB 2.7 supports deleting data by the following:

  • time range
  • measurement (_measurement)
  • tag

Cannot delete data by field

InfluxDB 2.7 does not support deleting data by field.

Once a delete request completes successfully, the deleted data is no longer queryable, but will remain on disk until the compaction service runs.

Delete data using the influx CLI

Use InfluxDB CLI connection configurations to provide your InfluxDB host, organization, and API token.

  1. Use the influx delete command to delete points from InfluxDB.

  2. Use the --bucket flag to specify which bucket to delete data from.

  3. Use the --start and --stop flags to define the time range to delete data from. Use RFC3339 timestamps.

  4. (Optional) Use the -p, --predicate flag to include a delete predicate that identifies which points to delete.

    Deleting data without a delete predicate deletes all data in the specified bucket with timestamps between the specified start and stop times.

Examples

Delete points in a specific measurement with a specific tag value
influx delete --bucket example-bucket \
  --start '1970-01-01T00:00:00Z' \
  --stop $(date -u +"%Y-%m-%dT%H:%M:%SZ") \
  --predicate '_measurement="example-measurement" AND exampleTag="exampleTagValue"'
Delete all points in a specified time range
influx delete --bucket example-bucket \
  --start 2020-03-01T00:00:00Z \
  --stop 2020-11-14T00:00:00Z

Delete data using the API

Use the InfluxDB API /api/v2/delete endpoint to delete points from InfluxDB.

POST http://localhost:8086/api/v2/delete

Include the following:

  • Request method: POST
  • Headers:
    • Authorization: Token schema with your InfluxDB API token
    • Content-type: application/json
  • Query parameters:
  • Request body: JSON object with the following fields:
    * Required
    • * start: earliest time to delete data from (RFC3339)

    • * stop: latest time to delete data from (RFC3339)

    • predicate: delete predicate statement

      Deleting data without a delete predicate deletes all data in the specified bucket with timestamps between the specified start and stop times.

Examples

Delete points in a specific measurement with a specific tag value
curl --request POST http://localhost:8086/api/v2/delete?org=example-org&bucket=example-bucket \
  --header 'Authorization: Token YOUR_API_TOKEN' \
  --header 'Content-Type: application/json' \
  --data '{
    "start": "2020-03-01T00:00:00Z",
    "stop": "2020-11-14T00:00:00Z",
    "predicate": "_measurement=\"example-measurement\" AND exampleTag=\"exampleTagValue\""
  }'
Delete all points in a specified time range
curl --request POST http://localhost:8086/api/v2/delete?org=example-org&bucket=example-bucket \
  --header 'Authorization: Token YOUR_API_TOKEN' \
  --header 'Content-Type: application/json' \
  --data '{
    "start": "2020-03-01T00:00:00Z",
    "stop": "2020-11-14T00:00:00Z"
  }'

For more information, see the /api/v2/delete endpoint documentation.

To delete a bucket see Delete a bucket.


Was this page helpful?

Thank you for your feedback!


New in InfluxDB 3.5

Key enhancements in InfluxDB 3.5 and the InfluxDB 3 Explorer 1.3.

See the Blog Post

InfluxDB 3.5 is now available for both Core and Enterprise, introducing custom plugin repository support, enhanced operational visibility with queryable CLI parameters and manual node management, stronger security controls, and general performance improvements.

InfluxDB 3 Explorer 1.3 brings powerful new capabilities including Dashboards (beta) for saving and organizing your favorite queries, and cache querying for instant access to Last Value and Distinct Value caches—making Explorer a more comprehensive workspace for time series monitoring and analysis.

For more information, check out:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On November 3, 2025, 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