Create a global Event Orchestration: POST /event_orchestrations with a name and team reference; note the orchestration's integration_key for use as the ingest endpoint
Configure the router layer: PUT /event_orchestrations/{id}/router with a rules array; each rule has conditions (field path + operator + value) and an actions object specifying route_to with a service ID
Add a catch-all rule as the last entry in the rules array with an empty conditions array to route unmatched events to a default service
Configure service-level rules: PUT /event_orchestrations/services/{service_id} with rules that can set severity, priority, suppress, suspend, or run automation actions
Send test events to https://events.pagerduty.com/v2/enqueue using the orchestration's routing_key to validate routing behavior
Migrate from deprecated Rulesets: as of January 31 2025, Rulesets are no longer visible in the PagerDuty web app; API access still works but new routing logic should use Event Orchestrations
Known gotchas
Event Orchestration routing rules are evaluated top-to-bottom and stop at the first match — order matters; place the most specific rules before broad catch-alls
Dynamic routing via pd_service_id in event custom details can route to arbitrary services, which may cause unintended alert delivery if events are not sanitized upstream
Rulesets reached UI end-of-life January 31, 2025; while API access persists, Atlassian recommends migrating to Event Orchestrations before full deprecation
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp