Webhook alerts to your own tools
A webhook channel sends every alert as a JSON POST to a URL you choose: a small script, an automation tool, a ticketing system, your own dashboard. The body has the event, the monitor's name and URL, the cause, when it happened and a dashboard link. Every request is signed so your endpoint can verify it came from heyUptime.
The request body
In short: One flat JSON object per alert. Fields are never renamed or removed; new ones may be added.
Example for a recovery: {"event": "recovered", "monitor": {"name": "Online shop", "url": "https://shop.example.com/"}, "cause": "HTTP 503 Service Unavailable", "occurred_at": "2026-10-08T14:17:00Z", "started_at": "2026-10-08T14:05:00Z", "dashboard_url": "https://heyuptime.com/app/monitors/42", "workspace": "Acme"}
| Field | Type | Meaning |
|---|---|---|
| event | string | down, recovered, ssl_expiring, domain_expiring, dns_changed or test |
| monitor.name | string | The monitor's name as shown in your dashboard |
| monitor.url | string | The address being checked; empty for a heartbeat (scheduled jobs have no address) |
| cause | string or null | down: the error. recovered: what the outage was. Reminders: the expiry date. dns_changed: what changed |
| occurred_at | string | When it happened, UTC, like 2026-10-08T14:05:00Z |
| started_at | string or null | recovered only: when the outage began, so you can compute the duration |
| dashboard_url | string | Link to the monitor in heyUptime (the Alerts page for a test) |
| workspace | string | Your workspace's name |
The headers and the signature
Every request carries three headers. The signature lets your endpoint reject anything that didn't come from heyUptime, and the timestamp stops an old request being replayed.
- Read the raw body bytes before parsing the JSON.
- Reject the request if the timestamp is more than 5 minutes from your clock.
- Compute HMAC-SHA256 over the string "<timestamp>." followed by the raw body, using the signing secret shown next to the channel on the Alerts page, and compare it with the header after "sha256=" using a constant-time comparison.
| Header | Value |
|---|---|
| X-HeyUptime-Event | down, recovered, ssl_expiring, domain_expiring, dns_changed or test |
| X-HeyUptime-Timestamp | Unix time in seconds when the request was sent |
| X-HeyUptime-Signature | sha256=<hex HMAC-SHA256 of "<timestamp>." + raw body, keyed by the channel's signing secret> |
Setting it up
- Make an HTTPS endpoint on the public internet that accepts a POST and answers with a 2xx. Private and internal addresses are refused.
- In heyUptime, open Alerts, press Add channel and choose Webhook. Paste the endpoint URL, add an optional name, and press Add Webhook channel.
- heyUptime generates a signing secret for the channel. It is shown on the Alerts page; copy it into your endpoint's configuration.
- Press Send test. Your endpoint receives a request with event "test"; the Alerts page shows the status code it answered with.
Delivery and retries
The last 20 deliveries, with the result of each, are listed on the Alerts page, so a broken endpoint is visible before you need it.
| Your endpoint answers | What heyUptime does |
|---|---|
| 2xx | Done |
| 408, 429 or 5xx, or no answer within 10 seconds | Retries after 30 seconds, then 2, 10 and 30 minutes, up to 5 attempts |
| 3xx | Stops: redirects aren't followed. Use the final URL |
| 401 or 403 | Stops and shows "Your webhook endpoint rejected the request" next to the channel |
| 404 or 410 | Stops and shows "Your webhook endpoint answered 404 Not Found" |
Every event a webhook receives
| Message | When it's sent |
|---|---|
| Down | A second check, 5 seconds after the first failure, confirms the site is down |
| Recovered | A check passes again; includes how long it was down |
| Certificate expiring | 14, 7, 3 and 1 days before the certificate's expiry date |
| Domain expiring | 30, 14, 7 and 1 days before the domain's registration runs out |
| DNS changed | Within an hour of the domain's A, AAAA, CNAME, NS or MX records changing |
| Test | When you press Send test on the Alerts page |
Which plans include webhooks
Webhooks are on every plan, including Starter at $5 a month, and during the 14-day trial, so you can build and test your endpoint before deciding.
| Plan | Included | Price |
|---|---|---|
| Starter | $5/mo (₹349 in India) | |
| Pro | $12/mo (₹849 in India) | |
| Business | $29/mo (₹1,999 in India) | |
| 14-day trial | Free, every channel unlocked, no card |
Questions
What can I do with a webhook?
Anything that accepts an HTTP request: create a ticket, post to a chat tool heyUptime doesn't support directly, flip a light in the office, log outages to a spreadsheet through an automation service, or hand it to a paging tool, since heyUptime has no on-call features of its own.
How do I verify the signature?
Take the X-HeyUptime-Timestamp header, build the string "<timestamp>." plus the raw request body, compute HMAC-SHA256 with the channel's signing secret, hex-encode it, and compare with the X-HeyUptime-Signature header after "sha256=" using a constant-time comparison.
Can I send a custom payload or extra headers?
No. The body and headers are fixed, which is what makes the signature reliable. Transform the JSON on your side.
Does it work with Zapier, Make or n8n?
Yes, any of them can receive a webhook. Use their "catch webhook" trigger, paste the URL it gives you into heyUptime, and press Send test to see the fields.
Is there an API to read my monitors?
No. Webhooks push alerts to you; there is no API for reading or creating monitors. CSV downloads of incidents and checks are available in the app.
Plug outages into whatever you run.
Add the endpoint, copy the signing secret, press Send test and read the JSON. Webhooks are unlocked for 14 days on every plan, no card.
Related
Updated October 8, 2026.