Integrations
Connect your monitoring and your alerts open and close themselves on your phone: a problem opens an alert (or updates the open one), and the recovery closes it, silently.
| Source | Page | URL |
|---|---|---|
| Any script or tool | Send API | https://api.zapapush.com/send |
| Tools with a "custom webhook" | Webhooks | https://api.zapapush.com/send |
| Prometheus Alertmanager | Alertmanager | https://api.zapapush.com/integrations/alertmanager |
| Grafana | Grafana | https://api.zapapush.com/integrations/grafana |
| AWS CloudWatch (SNS) | Cloud | https://api.zapapush.com/integrations/aws/YOUR_KEY |
| Google Cloud Monitoring | Cloud | https://api.zapapush.com/integrations/gcp?auth_token=YOUR_KEY |
| Azure Monitor | Cloud | https://api.zapapush.com/integrations/azure/YOUR_KEY |
| Cron jobs and servers that go quiet | Heartbeats | https://api.zapapush.com/heartbeat/<name> |
| Anything that sends email | Email to alert | alert+…@zapapush.com |
| Tools built for PagerDuty | PagerDuty | https://api.zapapush.com/v2/enqueue |
| Tools built for OpsGenie | OpsGenie | https://api.zapapush.com/v2/alerts |
Moving from another service? The PagerDuty and OpsGenie pages list how each of their integrations moves over.
Your key
Every integration uses the same key, from Settings in the app. Use whichever way your tool supports, in this order of preference:
- A header:
X-ZapaPush-Key: YOUR_KEY, orAuthorization: Bearer YOUR_KEY(GenieKeyfor OpsGenie tools). - Basic auth with the key as the password:
https://x:YOUR_KEY@api.zapapush.com/.... - In the URL:
/…/YOUR_KEYat the end of the path, or?key=YOUR_KEY.
Keys in URLs end up in logs, so prefer a header when the tool lets you set one. If a key leaks, rotate it in Settings.
How alerts open and close
- A problem opens an alert and buzzes your phone. Reports of the same problem update it (the counter goes up); if you acked it, they stay silent.
- The recovery closes it without a push. The next problem after that opens a new alert.
- Each source matches "the same problem" by its own ID: Alertmanager and Grafana by labels, PagerDuty by
dedup_key, OpsGenie byalias, the clouds by their alert IDs, heartbeats by name, email and the Send API by subject.
Limits
Every request counts as one post towards the 60 per minute of your key, however many alerts it carries. Heartbeat pings don't count.