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
Statuspage

Statuspage Pages API

The Pages API from Statuspage — 17 operation(s) for pages.

Documentation Provider Profile APIs.io OpenAPI GitHub

Statuspage Pages API is one of 4 APIs that Statuspage publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Pages. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 29 operations across 17 paths. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against a single base URL, https://api.statuspage.io/v1.

29 operations 17 paths 0 schemas 3 DELETE15 GET5 PATCH6 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.statuspage.io/v1
Authentication
API Key
Contact
Statuspage Support
Resource Areas
1

Authentication & Security 1

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

  • ApiKey — Pass Authorization: OAuth . The API key may alternatively be provided via the apikey query parameter.

Paths & Operations 29

Across 17 paths, the API surfaces 29 operations — 3 DELETE, 15 GET, 5 PATCH, 6 POST. Each is listed below with its method, path, parameters, and response codes.

Pages 29
GET
/pages
List pages
getPages → 200
GET
/pages/{page_id}
Get a page
getPagesByPageId 1 param → 200
PATCH
/pages/{page_id}
Update a page
patchPagesByPageId 1 param body → 200
GET
/pages/{page_id}/components
List components on a page
getPagesByPageIdComponents 1 param → 200
POST
/pages/{page_id}/components
Create a component
postPagesByPageIdComponents 1 param body → 201
GET
/pages/{page_id}/components/{component_id}
Get a component
getPagesByPageIdComponentsByComponentId 2 params → 200
PATCH
/pages/{page_id}/components/{component_id}
Update a component
patchPagesByPageIdComponentsByComponentId 2 params body → 200
DELETE
/pages/{page_id}/components/{component_id}
Delete a component
deletePagesByPageIdComponentsByComponentId 2 params → 204
GET
/pages/{page_id}/component-groups
List component groups
getPagesByPageIdComponentGroups 1 param → 200
POST
/pages/{page_id}/component-groups
Create a component group
postPagesByPageIdComponentGroups 1 param body → 201
GET
/pages/{page_id}/incidents
List incidents
getPagesByPageIdIncidents 1 param → 200
POST
/pages/{page_id}/incidents
Create an incident
postPagesByPageIdIncidents 1 param body → 201
GET
/pages/{page_id}/incidents/{incident_id}
Get an incident
getPagesByPageIdIncidentsByIncidentId 2 params → 200
PATCH
/pages/{page_id}/incidents/{incident_id}
Update an incident
patchPagesByPageIdIncidentsByIncidentId 2 params body → 200
DELETE
/pages/{page_id}/incidents/{incident_id}
Delete an incident
deletePagesByPageIdIncidentsByIncidentId 2 params → 204
GET
/pages/{page_id}/incidents/unresolved
List unresolved incidents
getPagesByPageIdIncidentsUnresolved 1 param → 200
GET
/pages/{page_id}/incidents/scheduled
List scheduled incidents
getPagesByPageIdIncidentsScheduled 1 param → 200
PATCH
/pages/{page_id}/incidents/{incident_id}/incident_updates/{incident_update_id}
Update an incident update
patchPagesByPageIdIncidentsByIncidentIdIncidentUpdatesByIncidentUpdateId 3 params body → 200
GET
/pages/{page_id}/maintenances
List scheduled maintenances
getPagesByPageIdMaintenances 1 param → 200
GET
/pages/{page_id}/maintenances/active
List active maintenances
getPagesByPageIdMaintenancesActive 1 param → 200
GET
/pages/{page_id}/maintenances/upcoming
List upcoming maintenances
getPagesByPageIdMaintenancesUpcoming 1 param → 200
GET
/pages/{page_id}/subscribers
List subscribers
getPagesByPageIdSubscribers 1 param → 200
POST
/pages/{page_id}/subscribers
Create a subscriber
postPagesByPageIdSubscribers 1 param body → 201
GET
/pages/{page_id}/subscribers/{subscriber_id}
Get a subscriber
getPagesByPageIdSubscribersBySubscriberId 2 params → 200
PATCH
/pages/{page_id}/subscribers/{subscriber_id}
Update a subscriber
patchPagesByPageIdSubscribersBySubscriberId 2 params body → 200
DELETE
/pages/{page_id}/subscribers/{subscriber_id}
Delete a subscriber
deletePagesByPageIdSubscribersBySubscriberId 2 params → 204
GET
/pages/{page_id}/metrics
List metrics
getPagesByPageIdMetrics 1 param → 200
POST
/pages/{page_id}/metrics
Create a metric
postPagesByPageIdMetrics 1 param body → 201
POST
/pages/{page_id}/metrics/{metric_id}/data
Add metric data points
postPagesByPageIdMetricsByMetricIdData 2 params body → 201

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

statuspage-pages-api-openapi.yml Raw ↑

Other APIs Statuspage publishes across the network.

Statuspage Manage API
AE Profile APIs.io
Statuspage Status API (v2)
AE Profile APIs.io
Statuspage Webhook Notifications
AE Profile APIs.io
#Pages
← Back to S APIs
API Details
ID
statuspage:statuspage-pages-api
Base URL
https://api.statuspage.io/v1
Docs
https://developer.statuspage.io/
Provider
Statuspage
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=statuspage-pages-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/statuspage-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 Statuspage 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.