UptimePad sends a JSON webhook when a monitor goes down or recovers, with incident context and enabled-region details in the payload. Payloads can be signed when you configure an endpoint secret. Webhooks unlock on Starter and above. Below: how UptimePad compares to UptimeRobot, Better Stack, StatusCake, and Pingdom on webhook capabilities.
| Tool | Webhooks on free tier | Custom payload | Per-monitor URL | Signed (HMAC) | Failure handling |
|---|---|---|---|---|---|
| UptimePad Starter: JSON webhooks with optional signing | No, Starter+ | ✓ | ✓ | ✓ | Non-2xx fails the send |
| UptimeRobot Check current plan | Check current plan | Check current docs | Check current docs | Check current docs | Check current docs |
| Better Stack Check current plan | Check current plan | Check current docs | Check current docs | Check current docs | Check current docs |
| StatusCake Check current plan | Check current plan | Check current docs | Check current docs | Check current docs | Check current docs |
| Pingdom Check current pricing | Check current pricing | Check current docs | Check current docs | Check current docs | Check current docs |
UptimePad sends a JSON request per state change with a stable alert shape. Payloads include the monitor identity, alert or recovery state, timestamp, incident ID when present, and alert-specific details such as status code, response time, region, DNS changes, or SSL expiry context.
{
"event": "alert",
"alertType": "http_down",
"severity": "critical",
"resolved": false,
"timestamp": "2026-05-03T14:22:18Z",
"subject": "Checkout is down",
"message": "checkout.acme.com returned 502",
"monitor": {
"id": "mon_4a7c8e",
"name": "checkout.acme.com",
"url": "https://checkout.acme.com/health"
},
"details": {
"statusCode": 502,
"responseTime": 842,
"region": "Region 1"
},
"incidentId": "inc_91a2",
"metadata": {}
}When you configure an endpoint secret, UptimePad adds anX-UP-SignatureHMAC-SHA256 header over the raw request body, plus anX-UP-Timestampheader. Verify the signature before trusting the payload.
A common mistake at scale: pointing every monitor at the same webhook URL and parsing monitor.id server-side. That works until a noisy monitor drowns out a critical one in your queue. UptimePad lets you set a different webhook URL per monitor, so checkout outages can hit your PagerDuty rotation while marketing-site flaps go to a low-priority Slack channel. If per-monitor routing matters, check each provider's current webhook docs before choosing a plan.
If your endpoint returns non-2xx, UptimePad treats that webhook delivery as failed instead of silently reporting success. For launch, the public promise is deliberately simple: signed JSON delivery, guarded outbound requests, test delivery from the dashboard, and clear failure handling. If you need durable receiver-side replay, make your endpoint idempotent and queue the payload after signature verification.
Yes, when you configure an endpoint secret. UptimePad includes an HMAC-SHA256 signature in the X-UP-Signature header, computed over the raw request body.
Yes. Each monitor can have its own webhook URL, or share a notification channel that fans out to multiple URLs. Common pattern: critical monitors go to PagerDuty, informational monitors go to a low-priority Slack channel.
The delivery fails if your endpoint returns non-2xx, so the notification path does not pretend the alert was accepted. Use the dashboard test delivery before relying on a webhook in production, and make your receiving endpoint idempotent.
No. Free uses email alerts only. Signed webhooks unlock on Starter and above, which keeps the free tier useful without turning it into a free alert fan-out service.
Webhook delivery is dispatched as part of the normal notification flow after a state change is confirmed. When regional consensus is enabled, confirmation can require agreement across configured regions to avoid false-positive alert storms.
Yes. The dashboard lets you send a test notification for the webhook channel before relying on it in production.
JSON webhook delivery on Starter and above, with optional signing and enabled-region incident context included.
Start monitoring free →