PagerDuty Events API is one of 38 APIs that PagerDuty publishes on the APIs.io network, described by an AsyncAPI event-driven specification.
Tagged areas include Alerting, Event, and Monitoring. The published artifact set on APIs.io includes API documentation, a getting-started guide, and an AsyncAPI specification.
This event API exposes
3 operations
across 3 channels,
and defines 35 schemas.
It is described by AsyncAPI 2.6.0, at version 1.0.0.
The API connects through 2 servers: {webhookUrl} (https), events.pagerduty.com (https).
3 operations3 channels35 schemas
Metadata
The identity and technical contract details declared by the specification.
Across 3 channels, the API surfaces 3 operations. Each is listed below with its action, channel, parameters, and response codes.
Channels 3
PUB
/pagerduty/webhook
Receive a PagerDuty V3 webhook event
receivePagerDutyWebhookbody
SUB
/v2/enqueue
Send an alert event to PagerDuty
sendEventV2body
SUB
/v2/change/enqueue
Send a change event to PagerDuty
sendChangeEventV2body
Messages & Schemas 35
The contract defines 35 schemas that model the data carried by its messages. The most detailed are IncidentEventData (19 properties), ServiceEventData (13 properties), EventsApiV2Body (8 properties), ResourceReference (5 properties). Each schema is shown below with its type and property counts.
IncidentTriggered
message
A new incident has been created on a service.
IncidentAcknowledged
message
A user or responder has acknowledged an incident.
IncidentUnacknowledged
message
An acknowledged incident has timed out and returned to triggered.
IncidentEscalated
message
An incident escalated to the next level of its escalation policy.
IncidentDelegated
message
An incident was reassigned to a different escalation policy.
IncidentReassigned
message
An incident was reassigned to a different user.
IncidentResolved
message
An incident has been resolved.
IncidentReopened
message
A previously resolved incident has been reopened.
IncidentAnnotated
message
A note has been added to an incident.
IncidentPriorityUpdated
message
The priority of an incident has been changed.
IncidentResponderAdded
message
A responder has been requested to join an incident.
IncidentResponderReplied
message
A responder has accepted or declined an incident response request.
IncidentStatusUpdatePublished
message
A status update has been posted to an incident.
IncidentConferenceBridgeUpdated
message
The conference bridge details on an incident have been modified.
IncidentCustomFieldValuesUpdated
message
One or more custom field values on an incident have been changed.
IncidentTypeChanged
message
The incident type assigned to an incident has been changed.
IncidentServiceUpdated
message
The service an incident belongs to has been updated.
IncidentWorkflowStarted
message
An incident workflow has started executing on an incident.
IncidentWorkflowCompleted
message
An incident workflow has finished executing on an incident.
ServiceCreated
message
A new service has been created.
ServiceUpdated
message
A service has been modified.
ServiceDeleted
message
A service has been deleted.
ServiceCustomFieldValuesUpdated
message
One or more custom field values on a service have been changed.
PageyPing
message
Test event delivered when a webhook subscription is pinged via POST /webhooksubscriptions/{id}/ping. The data object is empty.
EventsApiV2Request
message
Trigger, acknowledge, or resolve a PagerDuty alert.
EventsApiV2ChangeRequest
message
Record a change event on a service timeline.
WebhookEventEnvelope
object
Common envelope wrapping every V3 webhook delivery. The concrete data payload depends on eventtype / resourcetype.
1 property1 required
IncidentWebhookEnvelope
object
ServiceWebhookEnvelope
object
PingWebhookEnvelope
object
IncidentEventData
object
Incident resource snapshot at the time the webhook was emitted. Only the broadly stable fields are modelled here; additional keys are permitted because PagerDu…
19 properties
ServiceEventData
object
Service resource snapshot at the time the webhook was emitted.
13 properties
ResourceReference
object
Minimal reference to another PagerDuty resource.
5 properties
EventsApiV2Body
object
Common envelope for Events API v2 alert events. payload is required only when eventaction is trigger; for acknowledge and resolve only routingkey, eventaction,…
8 properties2 required
EventsApiV2ChangeBody
object
Request body for POST /v2/change/enqueue.
3 properties2 required
Specification
The full machine-readable AsyncAPI contract behind this narrative.
Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.
Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.
MCP tools for apis
4 tools reach this content
search_api_evangelistSearch every content type across the network at once.
find_relatedThe shared-tag relevance graph — what else covers this.
get_tagEverything one tag labels, across all content types.
guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
A second provider on the same verified email joins the account you already have.
Your account
ⓘWhere this information came from
This is an independent, third-party profile of PagerDuty Events API, published by
API Evangelist. We do not operate, host, resell, or
support these APIs, and we are not affiliated with or endorsed by the company unless stated above.
Everything here is built from publicly available information — the company's own site,
developer portal, documentation, public repositories, and the specifications it publishes for public use.
Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's
public API artifacts, scored against a published rubric. They are not certifications,
endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and
you do not need to justify the request. A removed company is recorded as unrated, never scored
zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy → On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.
