Webhook
Monitor outbound webhook event notification delivery and logs.
This page covers outbound webhook event notification delivery: JSON payloads, send history, and delivery logs. Open Webhook history and Webhook delivery logs in the admin console. For endpoint registration, HMAC signing, and admin controls, see Outbound Webhooks. For how visitors subscribe on /subscribe, see Webhook subscriptions.
When an event with Notifications enabled triggers a delivery, matching verified webhook subscribers receive an HTTPS POST with a JSON body describing the event at send time (type, severity, status, title, description, impact analysis when set, affected components, coordinator, timeline, and related fields). Description and impact analysis are flattened to plain text (lists and link URLs survive as characters; editor formatting is not markdown or HTML).
Every delivery is HMAC-signed — see Signing for verification details.
For how Visibility and subscription toggles affect delivery across channels, see Notifications overview — FAQ.
| Setting | Effect on webhook deliveries |
|---|---|
| Dashboard Visibility off | Deliveries still send with full event content. Dashboard links in the payload may not be publicly reachable. |
| Event not published | Deliveries still send when Notifications is on. |
| Subscriptions toggle off | Deliveries still send to existing verified endpoints. Sign-up and self-service manage flows are hidden; admins can still add endpoints on Outbound webhook endpoints. |
| Dashboard and event both public | Payload includes public dashboard/event context when applicable. |
Monthly integration message limit
Outbound webhook, Teams, Google Chat, and Slack deliveries share an organization monthly integration message limit (UTC calendar month). Usage appears on Overview and integration or notification screens.
- When the limit is reached, further deliveries are skipped (logged as skipped for quota) and are not retried.
- Event saves always succeed — the limit applies only to asynchronous outbound delivery.
Send history
Webhook history shows a UTC calendar-month bar graph of event notification webhook deliveries per day. Navigate 13 months of history with previous/next month controls. Counts match the event-notification portion of your combined integration delivery quota (history is tracked per channel). All bucketing uses UTC calendar days and months.
Delivery logs
Webhook delivery logs list individual delivery attempts. Each row includes:
| Field | Meaning |
|---|---|
| Endpoint | Redacted endpoint display (urlDisplay) |
| Status | Aggregate outcome — Accepted, Failed, or Skipped (see below) |
| HTTP status | Numeric response status when a response was received |
| Event / dashboard | Related event and dashboard when applicable |
| Error | Short client-side reason on failures (timeout, DNS, TLS, HTTP 4xx, and so on) |
Open a row for request and response bodies (may be truncated). Logs are retained for 30 days.
Each log includes a delivery timeline with one step — integration delivery is a single HTTP round-trip, not a multi-step provider lifecycle like email or SMS. Status reflects the endpoint's HTTP response, not delivery inside your webhook handler.
Status values
| Status | Meaning |
|---|---|
| Queued | Delivery job accepted |
| Accepted | Destination returned HTTP 2xx |
| Failed | HTTP or network failure |
| Skipped (suppressed) | Endpoint is on the suppression list — no HTTP call. Clear on Outbound webhook suppression or see Suppression. |
| Skipped (quota) | Monthly integration message limit reached |
| Skipped (feature) | Integrations entitlement not available at send time |
Delivery timeline
| Timeline step | When it appears |
|---|---|
| Endpoint accepted | HTTP 2xx response received |
| Endpoint rejected | HTTP 4xx/5xx response received |
| Request failed | Network error before a response (timeout, DNS, TLS, and so on) |
| Not attempted | Suppressed, quota, or feature skip — no HTTP call |
Frequently asked questions
Why does a delivery log show Skipped (suppressed)?
The endpoint was on your organization's suppression list when the notification was evaluated. Clear the entry on Outbound webhook suppression after the destination is fixed.
Where do admins manage webhook subscribers?
Not under email or SMS subscribers. See Outbound webhook endpoints.