How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

PagerDuty Change Events API

Change Events enable you to send informational events about recent changes such as code deploys and system config changes from any system that can make an outbound HTTP connection. These events do not create incidents and do not send notifications; they are shown in context with incidents on the same PagerDuty service.

PagerDuty Change Events API is one of 38 APIs that PagerDuty publishes on the APIs.io network, described by a machine-readable OpenAPI specification and an AsyncAPI event-driven specification.

Tagged areas include Change Events. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, authentication docs, a getting-started guide, and an AsyncAPI specification.

This API exposes 6 operations across 4 paths, and defines 5 schemas. It is described by OpenAPI 3.0.2, at version 2.0.0.

Requests are made against a single base URL, https://api.pagerduty.com.

6 operations 4 paths 5 schemas 4 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.2
API Version
2.0.0
Base URL
https://api.pagerduty.com
Authentication
API Key
Resource Areas
1

Authentication & Security 1

PagerDuty Change Events API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (api_key). By default, every request must be authenticated.

  • api_key — The API Key with format Token token=

Paths & Operations 6

Across 4 paths, the API surfaces 6 operations — 4 GET, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Change Events 6

Change Events enable you to send informational events about recent changes such as code deploys and system config changes from any system that can make an outbound HTTP connection…

GET
/change_events
PagerDuty List Change Events
listChangeEvents 9 params → 200400401403
POST
/change_events
PagerDuty Create a Change Event
createChangeEvent 2 params → 202
GET
/change_events/{id}
PagerDuty Get a Change Event
getChangeEvent 3 params → 200400401403404
PUT
/change_events/{id}
PagerDuty Update a Change Event
updateChangeEvent 3 params body → 200400401403404
GET
/incidents/{id}/related_change_events
PagerDuty List related Change Events for an Incident
listIncidentRelatedChangeEvents 4 params → 200400401403404
GET
/services/{id}/change_events
PagerDuty List Change Events for a service
listServiceChangeEvents 10 params → 200400401403404

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. Each schema is shown below with its type and property counts.

IntegrationReference
ChangeEvent
Reference
ServiceReference
Tag

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

pagerduty-change-events-api-openapi.yml Raw ↑

Other APIs PagerDuty publishes across the network.

PagerDuty Events API
PagerDuty Abilities API
PagerDuty Add-Ons API
PagerDuty Alert Grouping Settings API
PagerDuty Analytics API
PagerDuty Audit API
PagerDuty Automation Actions API
PagerDuty Business Services API
PagerDuty Change Tags API
PagerDuty Custom Fields API
PagerDuty Escalation Policies API
PagerDuty Event Orchestrations API
Where this information came from

This is an independent, third-party profile of PagerDuty Change 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.