Deprecated: create or replace the legacy single webhook for a monitor

Deprecated alias (issue #212), backed by recipients. If this monitor has no attached webhook-type recipient, creates one named after the monitor, attaches it, and returns it (with its secret) in the legacy shape. If one is already attached, this updates ITS url and returns the SAME id and secret — including when that recipient is shared with other monitors via PUT /api/v1/monitors/{monitorID}/recipients, in which case the URL change applies to every monitor sharing it, not just this one. Prefer POST /api/v1/recipients + PUT /api/v1/monitors/{monitorID}/recipients for new integrations. The url must point to a public hostname; private/loopback/link-local/mDNS URLs are rejected with 400 {"error":"url must be a valid http(s) URL"} (SSRF hardening).

put/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

Path parameters

monitorIDinteger required

Monitor ID.

Request body

urlstring uri required

Example request

{
  "url": "https://example.com/uptime-webhook"
}

Response

Webhook

idinteger
monitor_idinteger
urlstring uri
secretstring

HMAC-SHA256 signing secret. Prefix whs_live_.

created_atstring date-time

Changes

No recorded changes to this operation across all 1 revision of this API.