delivery says where changes go. The changes feed always has them; a webhook and email recipients are optional.
monitor.changes, once per check that found changes, and monitor.paused, when the monitor pauses itself for lack of credits or after repeated failures.
Webhooks
Each event is onePOST with a JSON body. Delivery retries on failure: five attempts, 1 minute, 5 minutes, 30 minutes and 2 hours apart. Any 2xx answer counts as delivered; redirects are not followed. GET /monitors/{id}/deliveries lists the attempts.
The URL must be public: loopback, private and link-local addresses are refused.
Headers
Payload: monitor.changes
changes has one entry per changed resource. patch is cut to 80 lines; the full one is on the result in the API. For a page compared as text, diff is null and patch carries the lines.
Payload: monitor.paused
Verifying the Signature
With asecret on the monitor, every request is signed: X-HasData-Signature is sha256= followed by the hex HMAC-SHA256 of <timestamp>.<raw body> under the secret, where <timestamp> is the X-HasData-Timestamp header. Compute it over the raw bytes, before parsing the JSON.
email.to (up to 10) gets a message per event: the changed resources with what changed, or the pause and its reason, each with a link to the monitor.
The AI Judge
Not every change matters. With agoal on the monitor, every changed result is judged by an AI model against it, and the verdict is stored on the result:
- The judge costs 2 credits per change it looks at, charged with the check.
- Webhooks and emails are sent only for changes the judge found to matter; the feed keeps every change, and
GET /monitors/changes?matters=truefilters it. - When the judge could not run, the verdict is
{ "error": "judge_unavailable" | "judge_failed" | "not_enough_credits", "message": "…" }and the change is reported as if it mattered.