docs

PagerDuty

ZapaPUSH accepts PagerDuty's Events API v2. If a tool can send to PagerDuty, it can send to ZapaPUSH: change the URL and use your ZapaPUSH key as the routing key. Nothing else in the tool's config changes.

Switch a tool over

PagerDuty ZapaPUSH
URL https://events.pagerduty.com/v2/enqueue https://api.zapapush.com/v2/enqueue
Routing / integration key your PagerDuty key your ZapaPUSH key

https://api.zapapush.com/integrations/pagerduty/v2/enqueue works too. The shorter URL is for tools where you can only change PagerDuty's base URL (https://api.zapapush.com).

curl -H 'Content-Type: application/json' https://api.zapapush.com/v2/enqueue -d '{
  "routing_key": "YOUR_KEY",
  "event_action": "trigger",
  "dedup_key": "db-1-disk",
  "payload": {"summary": "Disk full on db-1", "source": "db-1", "severity": "critical",
              "custom_details": {"used": "95%"}}
}'

What happens

event_action In ZapaPUSH
trigger Creates the alert and buzzes your phone. The same dedup_key again updates it; if it's acked, silently.
acknowledge Acks the alert, silently.
resolve Closes the alert, silently.
  • The alert title is [severity] summary, for example [critical] Disk full on db-1.
  • The description lists source, component, group and class, then each custom_details field, then the links and client_url.
  • Without a dedup_key, a trigger gets a new one, returned in the response like PagerDuty does. Use it to acknowledge or resolve.

Responses match PagerDuty's, so tools that check them keep working:

{"status": "success", "message": "Event processed", "dedup_key": "db-1-disk"}

That's status 202. Bad events and unknown keys get 400 with {"status": "invalid event", "message": "...", "errors": ["..."]}.

Move everything over

In PagerDuty, open each Service → Integrations and note what sends to it: Events API v2 (most monitoring tools), email integrations, and built-in ones (CloudWatch, Datadog, Grafana and so on). Then switch each one:

PagerDuty integration In ZapaPUSH
Events API v2 (any tool) URL https://api.zapapush.com/v2/enqueue, routing key = your ZapaPUSH key, as above.
Events API v1 Not supported: switch the tool to Events v2, or to its native ZapaPUSH integration below.
Email integration Your email to alert address.
Prometheus / Alertmanager Keep the Events v2 receiver with the new URL and key, or use the native Alertmanager receiver.
Grafana The Grafana webhook contact point.
AWS CloudWatch SNS to /integrations/aws.
Azure Monitor, Google Cloud Their webhooks: Cloud.
Maintenance windows, incident snooze Maintenance windows and snooze.

Run both side by side for a few days: most tools can send to two destinations, so you can compare before removing PagerDuty.

What's different

PagerDuty In ZapaPUSH
Services A group, with its own key. One group on Personal, unlimited on Business.
On-call schedules, escalation policies Business plan: on-call shifts in each group, then push, phone call and the next person.
Phone calls Business plan, as an escalation step (Phone calls).
SMS Not yet.
Routing rules, Event Orchestration, suppression Not yet. Every event goes to the key's group.
Change events (/v2/change/enqueue) Accepted and ignored.
images Ignored.
Incident response (status updates, postmortems, stakeholders) Not planned.

Switch offer

Teams moving from PagerDuty get 50% off the first year of a yearly Business plan (paid in advance, no refunds) with the code SWITCH50.

Limits

Each event counts as one post towards the 60-per-minute limit, the same as the Send API.