Webhooks: how they work and how to verify them

Signed JSON events fire on outage detected, contacts alerted, acknowledgement, and recovery. Verify the HMAC signature if you like.

The outgoing webhook POSTs a JSON event to your URL at each lifecycle moment: outage_detected (with outage kind and any regional-monitoring summary), contacts_alerted (per tier, with recipient names), contact_acknowledged, and recovered (distinguishing a device coming back from you confirming manually). A Send test event button delivers a sample immediately so you can build without waiting for a real outage.

Requirements and behavior:

URLs must be https and publicly reachable; private and internal addresses are rejected.
Deliveries retry a few times, then give up; a broken endpoint never delays or blocks your email and push alerts, which always send regardless.
Every delivery carries X-Proxigenta-Signature: t=<timestamp>,v1=<hex>, where v1 is HMAC-SHA256 of “t.” plus the raw body, keyed with your signing secret (shown in Integrations). Verify it to be certain events came from proxigenta. Most people can skip this.