# Delete a cluster monitor

## `DELETE /v1/clusters/{clusterId}/monitors/{alertId}`

Soft-deletes the monitor and retires its backend. Requires `monitors:write` and organization admin privileges. Retry to finish pending cleanup.

### Path parameters

- `clusterId` (string, required)
- `alertId` (string (uuid), required)

### Header parameters

- `Authorization` (string, required): `Bearer <token>`. [Authentication](https://spice.ai/docs/cloud/api/management#authentication) lists the tokens it accepts.
- `X-Org-Name` (string, optional): The organization to act on, by handle. Omit it to act on the organization the credential is bound to; sending it blank is a 400, not the same as omitting it. A user credential may name any organization its owner belongs to; a machine credential is pinned to its own. A portal session token is bound to none, so it must send this header on every route but `GET /v1/orgs` (400 `org_assertion_required` otherwise). Pattern: `^[A-Za-z0-9._-]{1,255}$`.

### Example request

```bash
curl -X DELETE "https://api.spice.ai/v1/clusters/<clusterId>/monitors/<alertId>" \
  -H "Authorization: Bearer <token>"
```

```http
DELETE /v1/clusters/<clusterId>/monitors/<alertId> HTTP/1.1
Host: api.spice.ai
Authorization: Bearer <token>
```

### Responses

**200 OK**

Monitor deleted

**400 Bad Request**

Invalid monitor ID

**401 Unauthorized**

Unauthorized

**403 Forbidden**

Insufficient scope or role

**404 Not Found**

Cluster or monitor not found

**500 Internal Server Error**

Internal server error

**502 Bad Gateway**

Backend cleanup failed

## `DELETE /v1/orgs/{orgId}/clusters/{clusterId}/monitors/{alertId}`

The org is `orgId` in the path. Soft-deletes the monitor and retires its backend. Requires `monitors:write` and organization admin privileges. Retry to finish pending cleanup.

### Path parameters

- `orgId` (integer, required): The org id from GET /v1/orgs. Minimum: `1`.
- `clusterId` (string, required)
- `alertId` (string (uuid), required)

### Header parameters

- `Authorization` (string, required): `Bearer <token>`. [Authentication](https://spice.ai/docs/cloud/api/management#authentication) lists the tokens it accepts.
- `X-Org-Name` (string, optional): When present, X-Org-Name must name the same org as orgId. Otherwise the request returns org\_path\_mismatch (400). Pattern: `^[A-Za-z0-9._-]{1,255}$`.

### Example request

```bash
curl -X DELETE "https://api.spice.ai/v1/orgs/<orgId>/clusters/<clusterId>/monitors/<alertId>" \
  -H "Authorization: Bearer <token>"
```

```http
DELETE /v1/orgs/<orgId>/clusters/<clusterId>/monitors/<alertId> HTTP/1.1
Host: api.spice.ai
Authorization: Bearer <token>
```

### Responses

**200 OK**

Monitor deleted

**400 Bad Request**

Invalid monitor ID. orgId is not a valid org id (`invalid_org_id`), or X-Org-Name does not name that org (`org_path_mismatch`).

**401 Unauthorized**

Unauthorized

**403 Forbidden**

Insufficient scope or role. The caller is not a member of the org (`org_forbidden`). A machine credential named a different org (`org_assertion_mismatch`). The org is deleted (`org_deleted`).

**404 Not Found**

Cluster or monitor not found

**500 Internal Server Error**

Internal server error

**502 Bad Gateway**

Backend cleanup failed

OpenAPI: [api.spice.ai/openapi.json](https://api.spice.ai/openapi.json)