Be the first to get access to new connectors. Get early access →
ConnectorBay Early access

PagerDuty Event Orchestrations (BYOK) — connector documentation

  • MCP endpoint: https://byok-pagerduty-event-orchestrations.connectorbay.com/mcp
  • REST API: POST https://byok-pagerduty-event-orchestrations.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-pagerduty-event-orchestrations.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own PagerDuty Event Orchestrations REST API key, sent in the X-Upstream-Key header of every request (never stored, logged or cached)
  • Health: https://byok-pagerduty-event-orchestrations.connectorbay.com/health · Tool schemas: https://byok-pagerduty-event-orchestrations.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-pagerduty-event-orchestrations · agent@connectorbay.com

What PagerDuty Event Orchestrations (BYOK) is for

PagerDuty Event Orchestrations (BYOK) lets an AI assistant read your own PagerDuty Event Orchestrations data through the PagerDuty Event Orchestrations API with a key you supply (REST API key). Read-only: 10 tools (list_orchestrations, get_orchestration, get_router_rules, get_global_rules, get_unrouted_rules, get_service_orchestration, get_service_orchestration_status, list_orchestration_cache_variables, list_service_cache_variables, list_rulesets). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.pagerduty.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by PagerDuty Event Orchestrations. PagerDuty Event Orchestrations and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

  • "Which PagerDuty event orchestrations do I have?"
  • "Show PagerDuty event orchestration PORCH01"
  • "How does PagerDuty orchestration PORCH01 route events to services?"
  • "What global rules does PagerDuty orchestration PORCH01 apply?"
  • "What happens to unrouted events in PagerDuty orchestration PORCH01?"
  • "What event rules does PagerDuty service PXYZ789 apply?"

What it does

  • list_orchestrations: List global event orchestrations with name, description, team, number of routes and update time. Routing keys are not returned by this tool.
  • get_orchestration: Get one global event orchestration by id: name, description, team, route count and version. Routing keys are not returned by this tool.
  • get_router_rules: Get the router rules of a global orchestration: rule sets with conditions and the service each rule routes to, plus the catch-all route.
  • get_global_rules: Get the global rules of an orchestration (applied to every event): rule sets with conditions and actions such as severity, priority, suppress or annotate, plus the catch-all.
  • get_unrouted_rules: Get the unrouted rules of an orchestration (applied to events that match no router rule).
  • get_service_orchestration: Get the service event orchestration of a service: rule sets with conditions and actions plus the catch-all.
  • get_service_orchestration_status: Tell whether events of a service are evaluated by its service orchestration (true) or by its legacy ruleset (false).
  • list_orchestration_cache_variables: List cache variables of a global orchestration (event data stored for use in rule conditions): name, source, regex and enabled state.
  • list_service_cache_variables: List cache variables of a service orchestration: name, source, regex and enabled state.
  • list_rulesets: List legacy rulesets (end-of-life event rules) with name, team and creation time. Routing keys are not returned by this tool.

BYOK key

You bring your own PagerDuty Event Orchestrations REST API key (https://support.pagerduty.com/main/docs/api-access-keys). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.pagerduty.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

Live from the PagerDuty Event Orchestrations API (api.pagerduty.com) with a BYOK key; documentation: https://developer.pagerduty.com/api-reference/. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by PagerDuty Event Orchestrations. PagerDuty Event Orchestrations and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your PagerDuty Event Orchestrations account.

Built for: Worldwide. Languages: English.