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 Response Plays API

Response Plays are a package of Incident Actions that can be applied during an Incident's life cycle.

PagerDuty Response Plays 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 Response Plays. 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 3 paths, and defines 7 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 3 paths 7 schemas 1 DELETE2 GET2 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 Response Plays 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 3 paths, the API surfaces 6 operations — 1 DELETE, 2 GET, 2 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Response Plays 6

Response Plays are a package of Incident Actions that can be applied during an Incident's life cycle.

GET
/response_playsdeprecated
PagerDuty List Response Plays
listResponsePlays 5 params → 200400401403
POST
/response_playsdeprecated
PagerDuty Create a Response Play
createResponsePlay 3 params body → 201400401403
GET
/response_plays/{id}deprecated
PagerDuty Get a Response Play
getResponsePlay 4 params → 200400401403404
PUT
/response_plays/{id}deprecated
PagerDuty Update a Response Play
updateResponsePlay 4 params body → 200401402403404
DELETE
/response_plays/{id}deprecated
PagerDuty Delete a Response Play
deleteResponsePlay 4 params → 204401403404
POST
/response_plays/{response_play_id}/rundeprecated
PagerDuty Run a response play
runResponsePlay 4 params body → 200400403429

Schemas 7

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

TeamReference
IncidentReference
UserReference
ResponsePlay
Reference
EscalationPolicyReference
Tag

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

pagerduty-response-plays-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 Events API
PagerDuty Change Tags API
PagerDuty Custom Fields API
PagerDuty Escalation Policies API
Where this information came from

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