# Webhook Monitor outbound webhook event notification delivery and logs. Source: https://statusdashboard.com/docs/notifications/webhooks > This is a plan-gated feature. If it isn't available in your account, visit the [Billing](/docs/org-mgmt/billing) page or contact support to review your options. This page covers outbound **webhook event notification** delivery: JSON payloads, send history, and delivery logs. Open [Webhook history](/app/notifications/webhooks/history) and [Webhook delivery logs](/app/notifications/webhooks/logs) in the admin console. For endpoint registration, HMAC signing, and admin controls, see [Outbound Webhooks](/docs/integrations/webhooks/outbound). For how visitors subscribe on `/subscribe`, see [Webhook subscriptions](/docs/status-dashboards/subscriptions/webhooks). 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](/docs/integrations/webhooks/outbound#signing) for verification details. For how **Visibility** and subscription toggles affect delivery across channels, see [Notifications overview — FAQ](/docs/notifications#frequently-asked-questions). | 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](/app/integrations/webhooks/outbound/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](/app) 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](/app/notifications/webhooks/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](/app/notifications/webhooks/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](/app/integrations/webhooks/outbound/suppression) or see [Suppression](/docs/integrations/webhooks/outbound#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](/app/integrations/webhooks/outbound/suppression) after the destination is fixed. **Where do admins manage webhook subscribers?** Not under email or SMS subscribers. See [Outbound webhook endpoints](/app/integrations/webhooks/outbound/endpoints).