JSON payload on every event
Receive a structured JSON body with monitor ID, status, affected regions, response time, and error detail on every down and recover event.
Send a signed JSON payload to any HTTPS endpoint when a monitor fires — customisable fields, automatic retries with exponential backoff, and delivery logs so you can debug every event.
Webhooks are the universal integration primitive. Whether you're routing alerts into a homegrown incident tool, creating Jira tickets, or feeding a Datadog event stream, the webhook endpoint is where Site Qwality hands off to your systems.
Receive a structured JSON body with monitor ID, status, affected regions, response time, and error detail on every down and recover event.
Every delivery includes an X-SiteQwality-Signature header so your receiver can verify the payload is genuine and untampered.
Failed deliveries are retried with exponential backoff — up to five attempts over 30 minutes — before the delivery is marked failed.
Choose which fields appear in the payload, add custom metadata, or filter events by severity so your receiver only handles what it needs.
Every webhook delivery is logged with the request headers, payload, response code, and latency — inspect and replay any event from the dashboard.
Send the same event to multiple endpoints — route one alert to a PagerDuty webhook and a custom audit log service simultaneously.
If your endpoint is down or returns a non-2xx response, Site Qwality retries with exponential backoff — 10s, 30s, 2m, 8m, 30m. Every attempt is logged with the HTTP status so you can see exactly what happened.
The webhook payload includes the monitor ID, name, URL, check type, current status, triggered-at timestamp, affected regions, HTTP status code or error, response time, and a link to the incident — enough to create a ticket or route an on-call page with no follow-up API calls.
retry attempts before a delivery is marked failed
median webhook delivery latency
webhooks on every plan, including free
of deliveries logged with full request and response
Every delivery includes an X-SiteQwality-Signature header containing an HMAC-SHA256 hash of the raw request body, signed with your webhook secret. Recompute the hash on your side and compare to verify authenticity.
By default, webhooks fire on monitor.down and monitor.recover. You can also enable monitor.degraded, incident.created, incident.resolved, and SSL or domain expiry events.
Site Qwality retries with exponential backoff at 10s, 30s, 2m, 8m, and 30m intervals. After five failed attempts, the delivery is marked failed and logged. You can replay it manually from the delivery log.
Yes. The webhook delivery log in the dashboard shows every attempt with the full payload, headers, response code, and latency. Any delivery can be replayed with one click or via the API.
Yes — webhooks are included on every plan, including the free tier. There is no limit on the number of endpoints or deliveries on paid plans.
Every product starts free — uptime, cron, synthetic, logs, RUM, incidents, and status pages. No credit card required.