Custom webhooks
Signed webhooks to any endpoint you run
Every incident, delivered as signed JSON to your own code. Feed PagerDuty, open tickets, trigger automation, or build the routing nobody ships out of the box.
Sentinel → your endpoint
Why webhooks
The escape hatch for everything we did not build
No monitoring tool ships an integration for your internal dashboard, your deploy bot, or the ticketing system your agency built in 2019. A signed webhook is the honest answer: Sentinel detects the incident and hands you the structured event, and your code decides what happens next.
It is also how Sentinel plugs into on-call tooling. Point the webhook at PagerDuty or Opsgenie and their escalation policies, rotations and phone calls sit downstream of Sentinel's multi-region detection.
- JSON payload with monitor, reason, severity, region and timestamps
- HMAC-SHA256 signature on every request, verified with your secret
- Fires on incident open and on recovery
- Included on the Pro plan and above
POST /hooks/sentinel · 12:51:12
X-Sentinel-Signature: sha256=9f2c41…
{
"event": "monitor.down",
"timestamp": "2026-08-04T12:51:12Z",
"monitor": {
"name": "acmestudio.co",
"url": "https://acmestudio.co"
}
}
POST /hooks/sentinel · 12:57:03
X-Sentinel-Signature: sha256=b81de0…
{
"event": "monitor.up",
"timestamp": "2026-08-04T12:57:03Z",
"monitor": {
"name": "acmestudio.co",
"url": "https://acmestudio.co"
}
}
Features
Everything a webhook should carry
Structured JSON payloads
Every incident posts as JSON with the monitor, failure reason, severity, region and timestamps. Parse it once and route it anywhere.
HMAC-SHA256 signatures
Each request is signed with your webhook secret, so your endpoint can verify the payload came from Sentinel and was not tampered with in transit.
Feed PagerDuty and friends
Point the webhook at PagerDuty's Events API, Opsgenie, or any incident tool that accepts HTTP, and Sentinel becomes the detection layer in front of your on-call rotation.
Build your own automation
Restart a container, open a ticket, flip a status flag, page a phone. If it has an HTTP endpoint, a Sentinel incident can trigger it.
Severity in the payload
Critical, warning and info arrive labelled, so your receiver can page for outages and quietly log the rest without a second lookup.
Recovery events too
Your endpoint hears when the incident resolves, not just when it opens, so downstream tickets and pages can close themselves.
What does the webhook payload look like?
A JSON body carrying the monitor details, what failed and why, the severity tier, the detecting region, and timestamps for the event. The docs include the full payload shape and a verification example.
How do I verify a webhook came from Sentinel?
Every request includes an HMAC-SHA256 signature computed with your webhook secret. Recompute the signature over the raw body on your side and compare. The setup guide has copy-paste verification code.
Can Sentinel alert PagerDuty?
Yes, via this webhook. Point it at a PagerDuty Events API integration and incidents open and resolve there automatically, which puts PagerDuty's on-call rotation downstream of Sentinel's checks. The same pattern works for Opsgenie and similar tools.
Which plans include webhooks?
Custom webhooks are included on the Pro plan and above. Slack, Discord and Teams alerts start on Starter, and email is on every plan including free.
What happens if my endpoint is down when an incident fires?
Delivery failures are logged against the notification so you can see what was missed. Your endpoint should return a 2xx quickly and process the payload asynchronously.
Wire Sentinel into your own stack
Detection from Sentinel, response from your code. Connect a webhook on the Pro plan.
No card for the free plan · 14-day trial on paid plans · Cancel anytime