AsyncAPI channel · PagerDuty · PagerDuty Events

/v2/enqueue

PagerDuty Events API v2 alert ingestion endpoint. Third-party tools POST a PD-CEF formatted JSON body to trigger, acknowledge, or resolve alerts on the integration identified by `routing_key`. Default rate limit is 480 events per minute per integration key.

Provider: PagerDuty AsyncAPI: v2.6.0 Spec: PagerDuty Events Operations: 1 Messages: 1

Channel address

/v2/enqueue

Operations

sendEventV2
Send an alert event to PagerDuty

Messages

EventsApiV2Request
Trigger, acknowledge, or resolve a PagerDuty alert.
Content-Type: application/json

About AsyncAPI

The AsyncAPI specification describes event-driven APIs the way OpenAPI describes request/response APIs. A channel is the named pipe — a webhook URL, a Kafka topic, a WebSocket route, an MQTT subject — that producers and consumers publish or subscribe to. Each channel carries one or more messages with structured payloads, and an operation declares whether a given party sends or receives on that channel.

Browse every event-driven channel on the APIs.io network or compare with the broader Naftiko capability, Agent Skill, and MCP server surfaces of the same providers.