AsyncAPI channel · Statuspage · Statuspage Webhook Notifications

/statuspage/webhook

Single subscriber endpoint that receives every Statuspage webhook event for the subscription. Subscribers should inspect the body to determine whether the payload is a component update, an incident update, or a scheduled maintenance update (incident payload with `scheduled_for`/`scheduled_until` populated).

Open source AsyncAPI → All Statuspage channels Statuspage provider profile
Provider: Statuspage AsyncAPI: v2.6.0 Spec: Statuspage Webhook Notifications Operations: 1 Messages: 3

Channel address

/statuspage/webhook

Operations

publish
receiveStatuspageWebhook
Receive a Statuspage webhook notification

Messages

ComponentUpdate
Dispatched whenever a component's status changes.
Content-Type: application/json
IncidentUpdate
Dispatched whenever an incident is created or updated.
Content-Type: application/json
ScheduledMaintenanceUpdate
Dispatched for scheduled maintenance lifecycle events. Statuspage reuses the incident webhook envelope; the maintenance is identified by non-null `incident.scheduled_for` and `incident.scheduled_until
Content-Type: application/json

About AsyncAPI

The AsyncAPI specification describes event-driven APIs the way OpenAPI describes request/response APIs. A channel is the named pipe — a webhook URL, a Kafka topic, a WebSocket route, an MQTT subject — that producers and consumers publish or subscribe to. Each channel carries one or more messages with structured payloads, and an operation declares whether a given party sends or receives on that channel.

Browse every event-driven channel on the APIs.io network or compare with the broader Naftiko capability, Agent Skill, and MCP server surfaces of the same providers.