---
title: "Delete monitor"
method: DELETE
path: "/v2/monitors/{monitorId}"
tags: ["monitors"]
---

# Delete monitor

`DELETE /v2/monitors/{monitorId}`

## Request

- Base URL: `https://api.cloudzero.com`
- URL: `https://api.cloudzero.com/v2/monitors/{monitorId}`
- Auth: API key in header `Authorization`
- TypeScript: <https://skmtc.dev/cloudzero/apis/cloudzero-api-v2-resources/docs/v2/monitors/:monitorId/delete.ts> (a function with typed inputs; its response is checked against the schema)

Deletes a monitor. It stops being evaluated, and its incidents drop out of `listIncidents`; `getIncident` still returns them, with `monitor_id` null. Deleting an already-deleted monitor returns the same response. Monitors created by CloudZero cannot be deleted.

## Path parameters

- `monitorId` string, required: The ID of the monitor

## Response `200`

Successful Response

- DeletedMonitor
  - `monitor_id` string, required: The ID of the deleted monitor
  - `status` 'deleted', required: Always `deleted`

## Other responses

- `401`: Unauthorized: the API key is missing or invalid (gateway `{"message": ...}` body), or the key carries no organization
- `403`: Forbidden. Either the API key lacks the scope for this operation (gateway `{"message": ...}` body), or the monitor was created by CloudZero and cannot be deleted.
- `404`: Not found: the resource does not exist or belongs to another organization
- `422`: A parameter failed validation; `details` lists each field failure when present

## Changes

- **2026-11-03** `56a692cf51b1`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/cloudzero/apis/cloudzero-api-v2-resources/changes/v2/monitors/:monitorId/delete.md)

---

[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.dev/cloudzero/apis/cloudzero-api-v2-resources/revisions/56a692cf51b1?raw)