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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
PagerDuty

PagerDuty Status Pages API

Status Pages can be public or private read-only pages, that display the status of some predefined set of services, to be shared with customers or internal stakeholders.

Documentation Provider Profile APIs.io OpenAPI GitHub

PagerDuty Status Pages 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 Status Pages. 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 27 operations across 16 paths, and defines 14 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.

27 operations 16 paths 14 schemas 4 DELETE16 GET4 POST3 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
Contact
PagerDuty Support
Resource Areas
1

Authentication & Security 1

PagerDuty Status Pages 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 27

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

Status Pages 27

Status Pages can be public or private read-only pages, that display the status of some predefined set of services, to be shared with customers or internal stakeholders.

GET
/status_pages
PagerDuty List Status Pages
listStatusPages 2 params → 200400401403404429
GET
/status_pages/{id}/impacts
PagerDuty List Status Page Impacts
listStatusPageImpacts 3 params → 200400401403404429
GET
/status_pages/{id}/impacts/{impact_id}
PagerDuty Get a Status Page Impact
getStatusPageImpact 3 params → 200401403404429
GET
/status_pages/{id}/services
PagerDuty List Status Page Services
listStatusPageServices 2 params → 200400401403404429
GET
/status_pages/{id}/services/{service_id}
PagerDuty Get a Status Page Service
getStatusPageService 3 params → 200401403404429
GET
/status_pages/{id}/severities
PagerDuty List Status Page Severities
listStatusPageSeverities 3 params → 200400401403404429
GET
/status_pages/{id}/severities/{severity_id}
PagerDuty Get a Status Page Severity
getStatusPageSeverity 3 params → 200401403404429
GET
/status_pages/{id}/statuses
PagerDuty List Status Page Statuses
listStatusPageStatuses 3 params → 200400401403404429
GET
/status_pages/{id}/statuses/{status_id}
PagerDuty Get a Status Page Status
getStatusPageStatus 3 params → 200401403404429
GET
/status_pages/{id}/posts
PagerDuty List Status Page Posts
listStatusPagePosts 5 params → 200400401403404429
POST
/status_pages/{id}/posts
PagerDuty Create a Status Page Post
createStatusPagePost 2 params body → 201400401403404429
GET
/status_pages/{id}/posts/{post_id}
PagerDuty Get a Status Page Post
getStatusPagePost 4 params → 200401403404429
PUT
/status_pages/{id}/posts/{post_id}
PagerDuty Update a Status Page Post
updateStatusPagePost 3 params body → 200400401403404429
DELETE
/status_pages/{id}/posts/{post_id}
PagerDuty Delete a Status Page Post
deleteStatusPagePost 3 params → 204401403404429
GET
/status_pages/{id}/posts/{post_id}/post_updates
PagerDuty List Status Page Post Updates
listStatusPagePostUpdates 4 params → 200400401403404429
POST
/status_pages/{id}/posts/{post_id}/post_updates
PagerDuty Create a Status Page Post Update
createStatusPagePostUpdate 3 params body → 201400401403404429
GET
/status_pages/{id}/posts/{post_id}/post_updates/{post_update_id}
PagerDuty Get a Status Page Post Update
getPostUpdate 4 params → 200401403404429
PUT
/status_pages/{id}/posts/{post_id}/post_updates/{post_update_id}
PagerDuty Update a Status Page Post Update
updateStatusPagePostUpdate 4 params body → 200400401403404429
DELETE
/status_pages/{id}/posts/{post_id}/post_updates/{post_update_id}
PagerDuty Delete a Status Page Post Update
deleteStatusPagePostUpdate 4 params → 204401403404429
GET
/status_pages/{id}/posts/{post_id}/postmortem
PagerDuty Get a Post Postmortem
getPostmortem 3 params → 200401403404429
POST
/status_pages/{id}/posts/{post_id}/postmortem
PagerDuty Create a Post Postmortem
createStatusPagePostmortem 3 params body → 201400401403404429
PUT
/status_pages/{id}/posts/{post_id}/postmortem
PagerDuty Update a Post Postmortem
updateStatusPagePostmortem 3 params body → 200400401403404429
DELETE
/status_pages/{id}/posts/{post_id}/postmortem
PagerDuty Delete a Post Postmortem
deleteStatusPagePostmortem 3 params → 204401403404429
GET
/status_pages/{id}/subscriptions
PagerDuty List Status Page Subscriptions
listStatusPageSubscriptions 4 params → 200400401403404429
POST
/status_pages/{id}/subscriptions
PagerDuty Create a Status Page Subscription
createStatusPageSubscription 2 params body → 201400401403404429
GET
/status_pages/{id}/subscriptions/{subscription_id}
PagerDuty Get a Status Page Subscription
getStatusPageSubscription 3 params → 200401403404429
DELETE
/status_pages/{id}/subscriptions/{subscription_id}
PagerDuty Delete a Status Page Subscription
deleteStatusPageSubscription 3 params → 204401403404429

Schemas 14

The contract defines 14 schemas that model the data the API accepts and returns. The most detailed are StatusPagePostUpdate (12 properties), StatusPagePost (11 properties), StatusPagePostUpdateRequest (10 properties), StatusPageSubscription (8 properties). Each schema is shown below with its type and property counts.

StatusPagePostPostRequest
object
Request schema for creating/updating a given Status Page Post resource.
7 properties 7 required
StatusPagePostUpdateRequest
object
Attributes for Post Update creation/update
10 properties 8 required
StatusPage
object
A Status Page with all the configuration needed to present the system status in a public or private manner.
6 properties
StatusPagePostUpdate
object
An update for a Post.
12 properties
StatusPagePostPutRequest
object
Request schema for creating a given Status Page Post resource.
6 properties 6 required
StatusPageSubscription
object
A StatusPageSubscription resource represents a subscription to a specific status page entity.
8 properties
StatusPagePost
object
A Post represents a communication resource presented in the Status Page about certain aspects of one or more services associated.
11 properties
StatusPageImpact
object
A StatusPageImpact resource represents a level of impact for a given Status Page Post.
6 properties
StatusPageSeverity
object
A Severity represents a level of impact for a given Status Page post.
6 properties
StatusPagePostmortem
object
A Postmortem represents a communication resource presented in the Status Page about follow-up made to a certain Post.
7 properties
StatusPageStatus
object
A Status represents a level of undergoing work and/or assessment for a given Status Page post.
6 properties
StatusPagePostmortemRequest
object
Request to create/update a given Postmortem resource.
4 properties 4 required
Pagination
object
4 properties
StatusPageService
object
A Service represents a PagerDuty service that is linked to a Status Page.
6 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

pagerduty-status-pages-api-openapi.yml Raw ↑

Other APIs PagerDuty publishes across the network.

PagerDuty Events API
AE Profile APIs.io
PagerDuty Abilities API
AE Profile APIs.io
PagerDuty Add-Ons API
AE Profile APIs.io
PagerDuty Alert Grouping Settings API
AE Profile APIs.io
PagerDuty Analytics API
AE Profile APIs.io
PagerDuty Audit API
AE Profile APIs.io
PagerDuty Automation Actions API
AE Profile APIs.io
PagerDuty Business Services API
AE Profile APIs.io
PagerDuty Change Events API
AE Profile APIs.io
PagerDuty Change Tags API
AE Profile APIs.io
PagerDuty Custom Fields API
AE Profile APIs.io
PagerDuty Escalation Policies API
AE Profile APIs.io
#Status Pages
← Back to P APIs
API Details
ID
pagerduty:pagerduty-status-pages-api
Base URL
https://api.pagerduty.com
Docs
https://developer.pagerduty.com/api-reference/
Provider
PagerDuty
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

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.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=pagerduty-status-pages-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/pagerduty-status-pages-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

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 Status Pages 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.