Webhook Payload Example

Structure and examples of the JSON payload sent by alert webhooks.

MoniTao webhooks send a structured JSON payload on each alert. This payload contains all the information needed to process the alert in your system.

You can use this payload to trigger automated actions, enrich your incident tickets, or feed your own dashboard.

Payload Structure

event: Event type: monitor.down, monitor.up, monitor.slow, heartbeat.missing.
monitor: Object containing the id, name, URL and type of the affected monitor.
status: HTTP code received, error message, measured response time.
timestamp: Event date and time in ISO 8601 format (UTC).

Payload Example

{
  "event": "monitor.down",
  "monitor": {
    "id": 12345,
    "name": "Production API",
    "url": "https://api.example.com/health"
  },
  "status": {
    "code": 503,
    "message": "Service Unavailable"
  },
  "timestamp": "2026-01-30T10:15:00Z",
  "duration_ms": 5420
}

Use Cases

Ticket creation: Automatically create a Jira ticket, GitHub Issue or ServiceNow on each alert.
Real-time dashboard: Feed your own status dashboard with MoniTao events.
Automation: Trigger automatic remediation actions (restart service, scale up).

Frequently Asked Questions

Is the payload the same for all monitor types?

The basic structure is identical. Some additional fields vary by type.

Can I request additional fields?

Is the webhook sent on recovery?

Yes, a monitor.up event is sent when the service becomes accessible again.

How to test the webhook without a real outage?

Use the "Send test" button in webhook settings.

Useful Links

Ready to Sleep Soundly?

Start free, no credit card required.

Create My Account See pricing