PagerDuty

Slug: pagerduty
Provider: PagerDuty Events API v2
Inbound ACK: No — users must ACK via the web dashboard

---

How it works

PSAPLink triggers a PagerDuty incident via the Events API v2 using a per-channel Integration Key (routing key). The incident appears in the PagerDuty timeline and can be escalated through PagerDuty's own on-call policies. PSAPLink does not receive PagerDuty acknowledgements — users must ACK in the PSAPLink web dashboard.

---

Configuration schema

Field	Type	Required	Description
integration_key	string	Yes	PagerDuty Events API v2 Integration Key (32-character routing key).
severity	string	No	Alert severity: critical, error, warning, info (default: critical).

---

Get a PagerDuty Integration Key

1. In PagerDuty, go to Services → select the target service (or create one).
2. Click Integrations → Add Integration → select Events API v2.
3. Copy the Integration Key.

---

Create a channel

POST /api/v1/transport-channels
Authorization: Bearer <token>
Content-Type: application/json

{
  "transport_type_slug": "pagerduty",
  "name": "Operations PagerDuty",
  "config": {
    "integration_key": "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
    "severity": "critical"
  }
}

---

Test the channel

POST /api/v1/transport-channels/{id}/test
Authorization: Bearer <token>

---

Limitations

• No inbound ACK. Acknowledging in PagerDuty does not resolve the PSAPLink notification — the user must also ACK in the PSAPLink web dashboard.
• PagerDuty deduplicates events by dedup_key; PSAPLink uses the delivery ID as the key.