AsyncAPI channel · PagerDuty · PagerDuty Events

/v2/change/enqueue

PagerDuty Events API v2 change event ingestion endpoint. Change events are informational signals from build, deploy, and configuration tooling that are not paged on but appear on the service timeline.

Open source AsyncAPI → All PagerDuty channels PagerDuty provider profile
Provider: PagerDuty AsyncAPI: v2.6.0 Spec: PagerDuty Events Operations: 1 Messages: 1

Channel address

/v2/change/enqueue

Operations

sendChangeEventV2
Send a change event to PagerDuty

Messages

EventsApiV2ChangeRequest
Record a change event on a service timeline.
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.