---
title: "Delete a telemetry stream"
method: DELETE
path: "/unit-cost/v1/telemetry/{telemetry_stream_name}"
tags: ["telemetry"]
---

# Delete a telemetry stream

`DELETE /unit-cost/v1/telemetry/{telemetry_stream_name}`

Mark a telemetry stream for deletion.  It may take several minutes for this operation to complete. During that time you will be unable to create a new telemetry stream with the same name. To force deletion of a stream that has associated data, send a JSON request body with `{"force": true}`. Note that some HTTP clients may not support request bodies on DELETE — if your client drops the body, use a tool like `curl` that supports it.

## Path parameters

- `telemetry_stream_name` string, required

## Headers

- `Authorization` string, required

## Request body

- object
  - `force` boolean — If `true`, forces deletion even if the stream has associated data. Without this flag, streams with data may not be deleted.

## Response `200`

Telemetry stream was marked for deletion

## Other responses

- `400` — Invalid request
- `403` — Not authorized, make sure you're using a valid API key in the header `Authorization`
- `429` — Rate limit exceeded. The API enforces rate limiting on incoming requests. Retry after a short delay.
- `503` — Service temporarily unavailable due to downstream capacity constraints. Retry after a short delay with exponential backoff.

---

[API](https://skmtc.dev/cloudzero/apis/cloudzero-api-v2-resources.md) · [All operations](https://skmtc.dev/cloudzero/apis/cloudzero-api-v2-resources/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/cloudzero/cloudzero-api-v2-resources/revisions/fd805a0e75e5/schema)