IntegrationsEvents API

PagerDuty Integration

Trigger deduplicated PagerDuty incidents from matching high-priority alerts.

5 min read•Last updated November 2026

Ensure critical security incidents never slip through the cracks. The ThreatPurge PagerDuty integration connects directly to the PagerDuty Events API v2, automatically triggering high-urgency incidents and paging on-call responders when critical threats emerge.

PagerDuty Incident Routing Overview#

When severe exposures occur outside business hours—such as an active stealer log session leak or an exposed database—security teams require immediate escalation. ThreatPurge routes critical threats directly to PagerDuty services, triggering on-call rotations and escalation policies without delay.

Events API Routing
Uses PagerDuty's native Events API v2 with deterministic deduplication keys, preventing alert storms while ensuring immediate escalation for P1 exposures.

Events API v2 Integration Setup#

Configuring PagerDuty takes only three steps in the Integration Centre:

1

Create Integration in PagerDuty

In PagerDuty, navigate to Services > Service Directory, select your security service, click 'Integrations', and add an 'Events API v2' integration.

2

Copy Integration / Routing Key

Copy the 32-character Integration Key generated by PagerDuty.

3

Configure in ThreatPurge Integration Centre

Navigate to Settings > Integration Centre, open the PagerDuty card, and paste the Routing Key.

4

Select Trigger Severity

Set the threshold to Critical only or High & Critical to prevent waking on-call staff for low-priority alerts.

5

Test & Activate

Click 'Test Incident Trigger' to trigger and automatically resolve a test page, confirming end-to-end routing.

Deduplication Keys & Auto-Resolution#

ThreatPurge attaches a deterministic deduplication key to each incident. When recurring threat scans detect the same compromised asset, PagerDuty correlates the event with the existing open incident, updating the incident timeline rather than paging on-call staff multiple times.

ThreatPurge ActionPagerDuty Event TypeResult in PagerDuty
New Critical Alert CreatedtriggerOpens new incident, pages on-call engineer according to escalation policy
Repeat Finding Observedtrigger (same dedup key)Appends details to existing incident timeline without duplicate paging
Alert Remediated / ResolvedresolveAutomatically closes the PagerDuty incident and resolves the on-call page

Severity & Urgency Mapping#

ThreatPurge alert severities map directly into PagerDuty event severities and urgency levels:

ThreatPurge SeverityPagerDuty SeverityPagerDuty Urgency
Critical (active session cookie, unauthenticated RDP)criticalHigh Urgency (immediate wake-up page)
High (verified phishing domain, expiring SSL < 15d)errorHigh Urgency (standard business escalation)
Medium (outdated web server, missing SPF)warningLow Urgency (silent dashboard notification)
Low (discovered subdomain)infoSuppressed from on-call paging

Was this page helpful?

Your feedback helps us improve ThreatPurge technical documentation.