Statuspage

Read Statuspage pages, components, groups, incidents, maintenances, subscribers and metrics; update component status and publish incidents and maintenance.

Keep the public or private status page in step with monitoring and the service desk, so customers see accurate status without manual updates.

Build a flow with Statuspage Provider API documentation

Source actions

Destination actions

Data types

Validation status

Implemented · fixture tested.

Implementation is checked against provider-shaped fixtures for every action, authentication failures, rate limits, pagination and duplicate safety. Provider sandbox and authorised account validation are recorded separately when credential-backed runs are completed.

What you can map

component groups

Create component group
Destination
Not retried automatically
Creates a group from existing components.
Get component group
Source
One component group.
List component groups
Source
Component groups with their member components.
Update component group
Destination
Duplicate protected
Renames a group or replaces its components.

component uptime

Get component uptime
Source
Uptime percentage and outage durations for a showcased component.

components

Create component
Destination
Not retried automatically
Adds a component to a page, optionally inside a group.
Get component
Source
One component and its status.
List components
Source
Components on a page with their current status.
Update component status
Destination
Duplicate protected
Sets a component's status or changes its name, description or group.

incidents

Create incident
Destination
Not retried automatically
Opens a realtime incident with affected components. Subscribers are notified only when Notify subscribers is true.
Get incident
Source
One incident or maintenance with its updates and affected components.
List incidents
Source
Incidents and maintenances on a page: all, unresolved, scheduled, upcoming or active maintenance.
Update incident
Destination
Duplicate protected
Posts an update, changes status or component impact, or edits a maintenance window. Subscribers are notified only when Notify subscribers is true.

maintenances

Schedule maintenance
Destination
Not retried automatically
Schedules a maintenance window with optional automatic transitions. Subscribers are notified only when Notify subscribers is true.

metrics providers

List metrics providers
Source
Connected metrics providers such as Datadog, New Relic or Pingdom.

metrics

List metrics
Source
System metrics shown on a page with their provider and latest data time.

pages

Get page
Source
One status page with its settings.
List pages
Source
Status pages the API key can access.

subscribers

List subscribers
Source
Page subscribers by type and state (read-only).

Authentication

API key

Plans and access

All Statuspage plans, including Free; private pages and some subscriber types depend on the plan. API keys belong to a user and act with that user's page access.

Test environment

A free Statuspage page works for testing.

Rate limits

1 request per second per API token (bursts of up to 5); HTTP 420 or 429 when exceeded.

Provider events

Webhook subscribers receive incident and component updates. Nexra event triggers are not yet available; flows run on demand or on a schedule.

Before you build a flow

Incident and maintenance writes never notify subscribers or post to Twitter unless Notify subscribers is explicitly true for that call.
Statuspage returns HTTP 420 for some rate-limit responses; Nexra treats it as a validation error, not a retryable limit.
Subscribers are read-only; creating, unsubscribing or messaging subscribers is not implemented.
Deleting components, groups and incidents, and editing postmortems or individual incident updates, are not implemented.
Creates have no idempotency key; uncertain writes are not repeated automatically.