AsyncAPI channel · PagerDuty · PagerDuty Events

/pagerduty/webhook

Single subscriber endpoint that receives every V3 webhook event delivered to a `webhook_subscription`. The envelope's `event.event_type` field identifies the event class. PagerDuty sends one event per HTTP POST and retries on non-2xx responses.

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

Channel address

/pagerduty/webhook

Operations

publish
receivePagerDutyWebhook
Receive a PagerDuty V3 webhook event

Messages

IncidentTriggered
A new incident has been created on a service.
Content-Type: application/json
IncidentAcknowledged
A user or responder has acknowledged an incident.
Content-Type: application/json
IncidentUnacknowledged
An acknowledged incident has timed out and returned to triggered.
Content-Type: application/json
IncidentEscalated
An incident escalated to the next level of its escalation policy.
Content-Type: application/json
IncidentDelegated
An incident was reassigned to a different escalation policy.
Content-Type: application/json
IncidentReassigned
An incident was reassigned to a different user.
Content-Type: application/json
IncidentResolved
An incident has been resolved.
Content-Type: application/json
IncidentReopened
A previously resolved incident has been reopened.
Content-Type: application/json
IncidentAnnotated
A note has been added to an incident.
Content-Type: application/json
IncidentPriorityUpdated
The priority of an incident has been changed.
Content-Type: application/json
IncidentResponderAdded
A responder has been requested to join an incident.
Content-Type: application/json
IncidentResponderReplied
A responder has accepted or declined an incident response request.
Content-Type: application/json
IncidentStatusUpdatePublished
A status update has been posted to an incident.
Content-Type: application/json
IncidentConferenceBridgeUpdated
The conference bridge details on an incident have been modified.
Content-Type: application/json
IncidentCustomFieldValuesUpdated
One or more custom field values on an incident have been changed.
Content-Type: application/json
IncidentTypeChanged
The incident type assigned to an incident has been changed.
Content-Type: application/json
IncidentServiceUpdated
The service an incident belongs to has been updated.
Content-Type: application/json
IncidentWorkflowStarted
An incident workflow has started executing on an incident.
Content-Type: application/json
IncidentWorkflowCompleted
An incident workflow has finished executing on an incident.
Content-Type: application/json
ServiceCreated
A new service has been created.
Content-Type: application/json
ServiceUpdated
A service has been modified.
Content-Type: application/json
ServiceDeleted
A service has been deleted.
Content-Type: application/json
ServiceCustomFieldValuesUpdated
One or more custom field values on a service have been changed.
Content-Type: application/json
PageyPing
Test event delivered when a webhook subscription is pinged via `POST /webhook_subscriptions/{id}/ping`. The `data` object is empty.
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.