PagerDuty Incident Workflows API
An Incident Workflow is a sequence of configurable Steps and associated Triggers that can execute automated Actions for a given Incident.
PagerDuty Incident Workflows 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 Incident Workflows. 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 15 operations across 9 paths, and defines 8 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.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 1
PagerDuty Incident Workflows 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 15
Across 9 paths, the API surfaces 15 operations — 3 DELETE, 6 GET, 4 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.
An Incident Workflow is a sequence of configurable Steps and associated Triggers that can execute automated Actions for a given Incident.
Schemas 8
The contract defines 8 schemas that model the data the API accepts and returns. The most detailed are Pagination (4 properties), IncidentWorkflowInstance (3 properties), CursorPagination (2 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from PagerDuty 12
Other APIs PagerDuty publishes across the network.
This is an independent, third-party profile of PagerDuty Incident Workflows 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.