How to Configure Custom Webhooks for Uptime Monitoring

Webhooks are the industry standard for linking services together. By configuring a custom webhook alert channel in Pingzo, you can forward structured, real-time JSON payloads to your servers, database loggers, serverless cloud functions (like Vercel or AWS Lambda), or workflow automation tools (like Zapier, Make, and Pipedream).

How Pingzo Webhooks Work

Whenever a monitor goes down or recovers, Pingzo sends an HTTP POST request to your configured webhook URL with a Content-Type: application/json header and a detailed JSON payload.

Webhook JSON Payload Schema

Every webhook event contains detailed metrics about the incident:

{
  "event": "monitor.down",
  "monitor_id": "mon_cl6739f4a00192837",
  "monitor_name": "Production API Gateway",
  "url": "https://api.yourdomain.com",
  "status": "down",
  "trigger_time": "2026-06-16T03:00:00.000Z",
  "incident": {
    "id": "inc_cl89d421e0283749",
    "error_message": "Response timeout after 10000ms"
  }
}

Adding a Custom Webhook Channel

1. Navigate to the Alert Channels settings in your Pingzo Dashboard.
2. Click Add Channel and select Webhook from the dropdown menu.
3. Enter your target HTTP/HTTPS destination URL (e.g. https://api.yourdomain.com/webhooks/alerts).
4. Click Save to add the channel.
5. Click Test next to the webhook to dispatch a mock test.notification payload to verify your endpoint parses it correctly.

Custom Header & Token Verification

To secure your webhook endpoint, we recommend appending a unique authorization query parameter to your webhook URL (e.g. https://api.yourdomain.com/webhooks/alerts?secret=your_token). Your receiving server can then inspect the query parameters and reject unauthorized requests.