Pushover integration

Pushover delivers alerts as push notifications to your own devices, at a priority set by the event.

What you need

Two values, both from Pushover.

User Key. Shown on your Pushover dashboard as soon as you log in. A group key works too.
App Token. Create an Application in Pushover and copy its API token.

Connect it

In the dashboard, go to Manage → Integrations and click the Pushover card. Give it a name, fill in User Key and App Token, then click Add integration.

Or through the API, with POST /integration/pushover:

curl -X POST https://api.siteqwality.com/integration/pushover \
  -H "Authorization: Bearer $SITEQWALITY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "friendly_name": "Ops phones",
    "user_key": "<pushover-user-or-group-key>",
    "app_token": "<pushover-application-api-token>"
  }'

All three fields are required. Neither credential is verified against Pushover at save time, and neither reads back in full.

Add it to a notification group

Right after you add the integration, the dashboard offers to do this for you: choose a group or create one, choose which monitors alert that group (the ones that already do, every monitor, or ones you pick), then send a test. If you skipped it, Route alerts on the integration’s card opens the same step. To do it by hand:

Go to Respond → Notifications. Click a group’s name to open it, or click Add group to make a new one.
Under Notifications, click Add notification method. Set Notification type to Pushover and choose this integration under Integration.
Click Done editing, then Save changes (Create group for a new group).

Through the API, create the channel with POST /notification:

curl -X POST https://api.siteqwality.com/notification \
  -H "Authorization: Bearer $SITEQWALITY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "notification_group_id": "<your-group-id>",
    "type": "pushover",
    "details": { "pushover_integration_id": "<pushover-integration-id>" }
  }'

Priority

Priority is set automatically per event type and is not configurable:

Event	Pushover priority
Monitor down	`1` (high, bypasses your quiet hours)
Monitor recovered	`0` (normal)
Domain expiry warning	`0` (normal)

Priority 2 (emergency, requires acknowledgment) is not used.

Delivery behavior

A send is attempted once, and a refusal from Pushover is recorded as rejected. Any other failure is run up to two more times, so a duplicate push is possible. If those runs fail too, the alert is dropped with no record in alert history. See delivery guarantees.

Limitations

Heartbeat (cron) monitors, TLS certificate alerts, page speed alerts and DNS record changes do not reach Pushover. See the coverage table.