Signed website change webhooks in real time.
Get website changes pushed into your own systems the moment they are found. WebChange Detector sends a signed JSON payload to your endpoint, so you can route changes into Slack, Jira, Linear or your own tools without polling.
From detection straight into your systems.
Four event types
Subscribe to the events you need: new change detected, check run completed, single check completed and single check failed.
HMAC signatures
Every live delivery carries an HMAC-SHA256 signature in its Signature header. Test deliveries from the dashboard are not signed, so accept unsigned requests while you test.
Automatic retries
If your endpoint is briefly down, the delivery is retried automatically, so a short outage does not cost you an alert.
Self-service
Manage webhook endpoints directly in your dashboard. Trigger simulated test payloads with one click to validate your receiver code before going live.
Any HTTPS endpoint
Works with any HTTPS receiver: a route in your app, a Node or Python server, AWS Lambda or Cloudflare Workers.
Stable payloads
Stable, additive-only JSON schemas. New event properties expand the payload without breaking existing webhook parsers.
From zero to verified webhooks in six steps.
All you need is an HTTPS endpoint that accepts JSON POST requests: a route in your app or a small serverless function.
Stand up an endpoint
An HTTPS URL that accepts POST requests, for example a route in your app or a relay into your ticket system.
Create the webhook
Add your endpoint URL in the dashboard and pick the event: new changes, finished check runs, or single checks that completed or failed.
Get your webhook secret
Your account has one webhook secret, returned by the account endpoint of the REST API (GET /api/v2/account). Store it in your environment variables.
Send a test delivery
Click Test next to your webhook in the dashboard. A sample payload of the chosen event goes to your endpoint, so you can check the JSON right away. Test deliveries are not signed.
Verify the signature
For live deliveries, compute the HMAC-SHA256 hash of the raw request body with your webhook secret and compare it with the Signature header. Reject the request if they differ.
Go live and stay idempotent
A retry can deliver the same event twice. Store the id from the payload, for example the comparison id, and skip anything you have already processed.
What a change event looks like.
Every event is a JSON POST with the same additive-only contract as the REST API: fields are added over time, never renamed or repurposed. A new-change event carries everything a receiver needs to act without a follow-up call (shortened example):
{
"id": "9b1f3c2e-4d5a-4b6c-8e7f-0a1b2c3d4e5f",
"url": "https://example.com/checkout/",
"html_title": "Checkout",
"device": "mobile",
"group_name": "example.com",
"difference_percent": 3.8,
"status": "new",
"public_link": "/show-change-detection?token=9b1f3c2e-4d5a-4b6c-8e7f-0a1b2c3d4e5f",
"ai_verification_result": {
"summary": "The place-order button is missing below the payment options."
},
"created_at": "2026-07-03T18:15:22.000000Z"
}
Verification is one HMAC comparison on the raw request body:
// PHP, verify before acting on the event
$rawBody = file_get_contents('php://input');
$signature = hash_hmac('sha256', $rawBody, $webhookSecret);
if (!hash_equals($signature, $_SERVER['HTTP_SIGNATURE'] ?? '')) {
http_response_code(401);
exit;
}
Retry behavior: if your endpoint is down, answers with a non-2xx status or takes longer than three seconds, the delivery is retried automatically with a growing pause between attempts. Answer fast and do slow work afterwards. A delivery can arrive twice, so use the id in the payload to spot duplicates.
Automation recipe: changes straight into your ticket system.
Point your webhook at a small relay that receives new-change events and creates a Jira or Linear ticket, with the AI summary as the issue title and the before and after link in the description. Check-run-completed events close the loop with a note in your team Slack channel. No polling, no manual logging, and visual bugs appear where developers already manage tickets. For no-code workflows, explore the Zapier integration.
Frequently asked questions
How do I verify the HMAC-SHA256 webhook signature?
Each live delivery includes a Signature header (test deliveries from the dashboard do not). In your receiver, compute the HMAC-SHA256 hex digest of the raw, unparsed request body with your account’s webhook secret and check that it matches the header.
What is the retry policy for failed webhook deliveries?
If your endpoint answers with an error status, takes longer than three seconds or cannot be reached, WebChange Detector retries the delivery automatically, with a growing pause between attempts.
Can I route webhooks per client subaccount?
Yes. Every subaccount has its own webhooks, set up in its dashboard or with its own API token, and they receive only that subaccount’s events. That way each client’s changes go to their own endpoint.
What event types are supported?
Four events: comparison_status_new (a new change was detected), batch_finished (a check run over several URLs is complete), queue_status_done (a single check of one URL and device is complete) and queue_status_failed (a single check failed).
How should I handle idempotency?
Each payload carries the id of the item it is about, for example the comparison id, and a timestamp. Because a retry can deliver an event twice, store the ids you have processed and skip repeats.
Can I test webhooks locally behind a firewall?
Yes. You can use tunneling tools like ngrok or Cloudflare Tunnel to expose your local development environment and receive real test payloads from the dashboard.
Related pages.
Catch the next visual bug before anyone else.
Start with a free trial, connect a site, and see your first before and after comparison today.