---
title: "Trash alert"
method: DELETE
path: "/alerts/{alert_configuration_id}"
tags: ["Alert"]
---

# Trash alert

`DELETE /alerts/{alert_configuration_id}`

This endpoint trashes a subscription- or customer-scoped alert. The alert is
soft-deleted: it stops firing immediately and no longer appears in fetch or list
responses, while the underlying record is retained internally for audit.

Plan-level alerts cannot be trashed via the API — disable them instead
(`POST /v1/alerts/{alert_configuration_id}/disable`). Their removal would need to be
unwound from every subscription the alert was propagated to, which isn't supported yet.

## Path parameters

- `alert_configuration_id` string, required

## Response `204`

No Content

## Other responses

- `400` — Bad Request
- `401` — Unauthorized
- `404` — Not Found
- `409` — Conflict
- `413` — Content Too Large
- `429` — Too Many Requests
- `500` — Internal Server Error

## Changes

- **2026-07-01** `2580a0ee8d4c` — 1 info
  - endpoint added

[Change history](https://skmtc.dev/orbcorp/apis/api-reference/changes/alerts/:alert_configuration_id/delete.md)

---

[API](https://skmtc.dev/orbcorp/apis/api-reference.md) · [All operations](https://skmtc.dev/orbcorp/apis/api-reference/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/orbcorp/api-reference/revisions/2580a0ee8d4c/schema)