---
title: "Deprecated: remove the legacy single webhook from a monitor"
method: DELETE
path: "/api/v1/monitors/{monitorID}/webhook"
deprecated: true
---

# Deprecated: remove the legacy single webhook from a monitor

`DELETE /api/v1/monitors/{monitorID}/webhook`

## Request

- Base URL: `https://api.uptimemonitoring.com`
- URL: `https://api.uptimemonitoring.com/api/v1/monitors/{monitorID}/webhook`
- Auth: HTTP bearer

> **Deprecated.**

Deprecated alias (issue #212). Detaches the attached webhook-type
recipient from this monitor; deletes the recipient itself only if,
after detaching, it is attached to no other monitor and is not
marked `default` — a shared or default recipient survives with its
other attachments intact. Prefer
`PUT /api/v1/monitors/{monitorID}/recipients` to detach without
risking deletion of a shared recipient.

## Path parameters

- `monitorID` integer, required

## Response `204`

Deleted

## Other responses

- `404`: Monitor or webhook not found
- `429`: Per-account dispatcher rate limit exceeded (200 requests/minute). The `Retry-After` header gives the integer seconds until at least one token has refilled. The `X-RateLimit-*` trio reflects the bucket whose rejection produced this response — usually the global 200/min cap; on `POST /api/v1/monitors` a 429 may instead reflect the per-route 20/min creation limit.

---

[API](https://skmtc.dev/uptimemonitoring/apis/uptimemonitoring-com-api.md) · [All operations](https://skmtc.dev/uptimemonitoring/apis/uptimemonitoring-com-api/llms.txt) · [OpenAPI document](https://skmtc.dev/uptimemonitoring/apis/uptimemonitoring-com-api/revisions/ddcb2a8bc70f?raw)