Create and route PagerDuty incidents via Events API v2

domain: pagerduty.com · 4 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Create an Events API v2 integration on a service → routing key
  2. POST https://events.pagerduty.com/v2/enqueue with routing_key, event_action:'trigger', payload {summary, source, severity}
  3. Use dedup_key to group repeats of the same problem (same key = same incident)
  4. Send event_action 'resolve' with the same dedup_key on recovery

Known gotchas

Related routes

Trigger, acknowledge, and resolve incidents using the PagerDuty Events API v2
developer.pagerduty.com · 5 steps · unrated
Route security alerts to on-call via the PagerDuty Events API v2
developer.pagerduty.com · 5 steps · unrated
Automate an incident response runbook in PagerDuty using Incident Workflows and Automation Actions, capturing evidence at each step
support.pagerduty.com · 5 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans