Webhooks Configuration
Enterprise-grade uptime monitoring for DevOps. Route real-time incident alerts, status changes, and recovery notifications directly to your internal systems, Slack channels, or PagerDuty workflows.
Configure Your Webhook Endpoint
StatusPulse sends HTTPS POST requests to your designated endpoint whenever a monitored resource crosses your defined thresholds. You can configure up to ten distinct webhook targets per account, each with independent retry policies and signature verification keys.
Begin by navigating to Settings > Integrations > Webhooks in your StatusPulse dashboard. Enter a descriptive name and your endpoint URL. We recommend using a dedicated path to isolate routing logic. Set your preferred HTTP method and configure the timeout window. StatusPulse uses a standard three-second timeout followed by three exponential backoff retries before marking the delivery as failed.
Payload Structure & Signature Verification
Every webhook delivery contains a standardized JSON body and a cryptographic signature to ensure request authenticity. StatusPulse appends the X-StatusPulse-Signature header to each request, generated using HMAC-SHA256 with your endpoint secret key.
The payload schema remains consistent across all event types. Below is a reference breakdown of the core fields delivered during a status_down event:
event_type
String identifier for the trigger. Examples: status_down, status_up, ssl_expiring_soon, response_time_threshold.
monitor_id & monitor_name
Unique UUID and human-readable label for the affected asset. Example: urn:sp:monitor:8f4a2c91 / api.stripe-payment-gateway.
timestamp & region
ISO 8601 UTC timestamp of detection and the probe location. Example: 2024-05-12T14:32:09Z / us-east-1.
metadata
Nested object containing HTTP status codes, response latency in milliseconds, and consecutive failure count.
To verify signatures, extract the secret key from your webhook settings, compute the HMAC-SHA256 hash of the raw request body, and compare it against the header. Requests failing verification will be silently dropped by your endpoint for security.
Testing & Delivery Diagnostics
Validate your integration pipeline before relying on it for production incident routing. StatusPulse provides built-in diagnostic tools to simulate events, inspect raw payloads, and review delivery histories.
Use the Send Test Event action in your webhook configuration panel to trigger a synthetic status_down payload. This bypasses actual monitor thresholds and routes immediately to your endpoint. Check your server logs or request inspector to confirm receipt and signature validation.
If your endpoint returns a non-2xx status code, StatusPulse logs the failure and applies the configured retry schedule. You can view the complete delivery history, including response headers, latency metrics, and raw request bodies, under Settings > Integrations > Webhook Logs. Common resolution steps include verifying TLS 1.2 compatibility, whitelisting StatusPulse egress IPs, and ensuring your routing middleware does not block application/json headers.