Home
Pricing
Platform Blog About Contact FAQ Partners
Sign in Start free
Webhooks

Any alert, any endpoint,
your integration.

Signed JSON events to any endpoint you control, with retries for over a day and a delivery log you can replay from.

Free tier included No credit card 2-minute setup
Site Qwality integrations: Slack, webhooks, Telegram, Discord, Microsoft Teams and moreSite Qwality integrations: Slack, webhooks, Telegram, Discord, Microsoft Teams and more

Build any integration on top of webhooks.

Route alerts into a homegrown incident tool, open Jira tickets or feed an event stream. The webhook endpoint is where Site Qwality hands off to your systems.

JSON payload on every event

Each delivery is a JSON envelope with the event, its severity and its details, down to the full check result for a monitor.

Standard Webhooks signatures

Every delivery is signed to the Standard Webhooks spec, so its libraries verify it in one call and reject forged or stale ones.

Automatic retries with backoff

A failed delivery is retried with growing waits for over a day, so an endpoint that is down overnight still gets the alert.

Selectable payload fields

Choose the payload fields, add your own metadata keys, and filter by event or minimum severity.

Delivery log and replay

Every delivery is logged with the request, the response and how long it took. Replay any of them for 30 days.

Multiple endpoints per monitor

Send the same event to several endpoints, such as your incident tool and an audit log service.

Reliable delivery

Down overnight,
still delivered.

If your endpoint is unreachable or returns a 5xx, Site Qwality keeps retrying with growing waits for over a day. Every attempt is logged with its status.

  • Retries with backoff for over a day
  • Every attempt logged with its status code and an extract of the response body
  • Replay any past delivery from the dashboard or the API
app.siteqwality.com / webhooks / deliveries
POST /hooks/incident-tool DeliveredLIVE
ATTEMPTS2
FINAL STATUS200
SIGNEDv1
attempt 1timeout
attempt 2200 OK
payload size1.4 KB
signatureHMAC-SHA256
Full event payload

Every field your
integration needs.

Every delivery carries the delivery id, the event name, a severity, a timestamp and your account id. For an HTTP monitor, data holds the check result, down to the per-phase timing.

  • Monitor id, status, URL, HTTP code and failure reason in one payload
  • RFC 3339 timestamps on the envelope
  • Custom key-value metadata you define per endpoint
example payload{
  "id": "6ddbec4d-0b7e-4c1a-8f52-3e9d1a7c2b40",
  "event": "monitor.down",
  "severity": "critical",
  "created_at": "2026-03-14T09:26:54.218Z",
  "account_id": "2f6b9e14-7c3d-4a58-b1e0-94d2c7a3f615",
  "data": {
    "http_job_id": "8f1c3a92-5d47-4e1b-9c60-2ab7d5f80e31",
    "status": "failed",
    "request_uri": "https://api.acme.com/checkout",
    "response_http_code": 503,
    "failure_reason": "status",
    "check_region": "aws-us-east-1",
    "request_duration_ms": 184,
    "ttfb_ms": 171,
    "created_at": "2026-03-14T09:26:53.104Z",
    …
  }
}
Verifying a delivery

Verify a delivery
in one call.

Deliveries follow the Standard Webhooks spec, so its libraries for Node, Python, Go and Ruby verify them in one call and reject forged or stale ones.

  • Pass the exact bytes we sent, before any JSON parsing
  • Use the whsec_ secret exactly as shown
  • When you rotate, choose how long the old secret keeps working, up to 7 days
verify.js// npm install standardwebhooks
const { Webhook } = require('standardwebhooks');

// The whsec_ secret, exactly as shown.
const wh = new Webhook(secret);

// rawBody must be the exact bytes we sent, before JSON.parse.
// Throws on a bad signature or a delivery over 5 minutes old.
const event = wh.verify(rawBody, req.headers);
24h+

of retries with backoff before a delivery is marked failed

$0

webhooks on every plan, including free

30d

of deliveries logged, each one replayable

10

custom metadata keys you can add to every delivery

FAQ

Deliveries follow the Standard Webhooks spec, and its libraries do the whole check. In Node it is new Webhook(secret).verify(rawBody, headers), and Python, Go and Ruby have the same call. After you rotate a secret, deliveries are signed under both secrets for the period you choose.

Monitors going down and recovering, incident changes, TLS and domain expiry, DNS record changes, page speed drops, alert rules and real user monitoring issues. All are on by default, and you can filter them per endpoint by event or minimum severity. The webhook docs list every event.

Site Qwality retries with growing waits for over a day, so an endpoint that is down overnight still gets the event. A delivery that still fails is marked failed, and you can replay it from the delivery log.

Yes, for 30 days, from the delivery log in the dashboard or through the API. A replay resends the original body with a fresh signature and keeps the original webhook-id, so a receiver that drops duplicates by id handles it once.

Yes. Webhooks are included on every plan, including the free tier.

Start free. No credit card.

Uptime, cron, synthetic, logs, RUM, incidents, and status pages. Free tier on every product.