PagerDuty Integration

Connect PulsAPI to PagerDuty so that critical third-party outages automatically page your on-call engineer. When PulsAPI detects a major status change at AWS, Stripe, GitHub, or any other monitored service, it fires an event directly into PagerDuty's incident management system.

Prerequisites

• A PagerDuty account with permission to add integrations to a service
• A PulsAPI Business plan (or above)

Setup

Step 1 — Create a PagerDuty Events API V2 Integration

1. Log in to PagerDuty and go to Services → Service Directory.
2. Select the service that should receive PulsAPI alerts (or create a new one).
3. Click the Integrations tab, then click Add an integration.
4. Search for Events API V2 and click Add.
5. Copy the Integration Key (also called routing key) — a 32-character alphanumeric string.

Step 2 — Connect in PulsAPI

1. Go to Settings → Integrations.
2. Click Connect under PagerDuty.
3. Paste your Integration Key in the PagerDuty Routing Key field.
4. Give the integration a label (e.g., "PagerDuty — Critical Vendors").
5. Click Test — a test incident should appear in PagerDuty within a few seconds.
6. Click Save.

Severity mapping

PulsAPI maps service status to PagerDuty event severity automatically:

When a service recovers to Operational, PulsAPI sends a resolve event to PagerDuty, automatically resolving the open incident.

Incident payload

PulsAPI sends the following data to PagerDuty with each event:

{
  "routing_key": "your_integration_key",
  "event_action": "trigger",
  "payload": {
    "summary": "AWS EC2 status changed to Major Outage",
    "severity": "critical",
    "source": "PulsAPI"
  }
}

Troubleshooting

Test incident not appearing in PagerDuty?

• Verify the routing key is exactly 32 characters with no leading or trailing spaces
• Ensure the PagerDuty service is active (not in maintenance mode)
• Check that Events API V2 is the selected integration type — not the older Events API V1

Incidents not being resolved automatically?

Resolve events are sent when a service returns to Operational status. If PagerDuty incidents remain open after a service recovers, check that your PagerDuty service is not configured to suppress resolve events.

Multiple incidents for the same outage?

If you have multiple PagerDuty integrations (e.g., one per environment), ensure each uses a distinct routing key. Duplicate routing keys will create duplicate incidents.