Webhooks
Many tools have a "webhook" or "custom HTTP notification" option: uptime monitors, CI servers, home automation, NAS boxes, Zabbix, Netdata, Jenkins, Uptime Kuma. Point it at the Send API.
The settings
| Setting | Value |
|---|---|
| URL | https://api.zapapush.com/send |
| Method | POST |
| Header | X-ZapaPush-Key: YOUR_KEY |
| Body | JSON {"subject": "...", "description": "..."}, or plain text |
If the tool can't set headers, use https://api.zapapush.com/send/YOUR_KEY.
Body templates
Most tools let you write the body with their own placeholders. Put the short headline in subject and the
details in description:
{
"subject": "{{monitor_name}} is DOWN",
"description": "{{message}}\n{{url}}"
}
The placeholder names differ per tool; check its docs. If the tool only sends its own fixed JSON, send it to
/send anyway with title or message fields, or wrap it in a small script that posts the subject you want.
Plain text works too: the first line is the subject, the rest the description.
Up and down alerts
The Send API matches alerts by subject. To have "up" close the "down" alert automatically, use one of the integrations with open and close, such as the PagerDuty Events API, which most uptime tools support:
- DOWN →
"event_action": "trigger"with adedup_keyper monitor - UP →
"event_action": "resolve"with the samededup_key
Test it
curl -H 'X-ZapaPush-Key: YOUR_KEY' -H 'Content-Type: application/json' \
-d '{"subject":"TEST webhook","description":"Sent with curl"}' https://api.zapapush.com/send