GET /v1/admin/status-page
Read the status page editor view
- operationId
getAdminStatusPage- Auth
- Session: the Bearer session of a signed-in control plane user, used by the customer in their own control plane; a plugin must never ask for it.
- Required permissions
All of:system_configuration.read
Responses
getAdminStatusPage Responses| Status | Description |
|---|
200 | Settings Fields:revision: integer(int64) settings: Settings components: array<AdminComponent> incidents: array<Incident> line_groups: array<object> updated_at: string(date-time) |
|---|
401 | Error |
|---|
403 | Error |
|---|
503 | Error |
|---|
What to do on failure
401 Check the credential format and whether it expired or was rotated.403 Check the key scopes, the owner’s current permissions and the tenant scope; never switch to a more privileged account.503 A dependency is unavailable: retry later with the original Idempotency-Key.
↑ Back to list
PUT /v1/admin/status-page
Save the status page settings and components
- operationId
updateAdminStatusPage- Auth
- Session: the Bearer session of a signed-in control plane user, used by the customer in their own control plane; a plugin must never ask for it.
- Required permissions
All of:system_configuration.manage
Parameters
updateAdminStatusPage Parameters| Name | In | Type | Required | Description |
|---|
If-Match | header | string | Yes | — |
|---|
Request body
application/json · Required:Yes
updateAdminStatusPage Request body| Name | Type | Required | Description |
|---|
settings | SettingsInput | Yes | — |
|---|
components | array<ComponentInput> | Yes | — |
|---|
Responses
updateAdminStatusPage Responses| Status | Description |
|---|
200 | Saved view Fields:revision: integer(int64) settings: Settings components: array<AdminComponent> incidents: array<Incident> line_groups: array<object> updated_at: string(date-time) |
|---|
400 | Error |
|---|
401 | Error |
|---|
403 | Error |
|---|
409 | Duplicate component name |
|---|
412 | Revision conflict |
|---|
428 | If-Match revision is missing |
|---|
503 | Error |
|---|
What to do on failure
400 Fix the parameters or body per the field list; do not retry unchanged.401 Check the credential format and whether it expired or was rotated.403 Check the key scopes, the owner’s current permissions and the tenant scope; never switch to a more privileged account.409 Read the current state first; a retry of the same operation keeps the original Idempotency-Key and body.412 The revision changed: read the latest ETag, decide again, then send the new If-Match.428 A precondition is missing: read the resource and send If-Match (or the required proof).503 A dependency is unavailable: retry later with the original Idempotency-Key.
↑ Back to list
POST /v1/admin/status-page/incidents
Create an incident or a scheduled maintenance
- operationId
createStatusPageIncident- Auth
- Session: the Bearer session of a signed-in control plane user, used by the customer in their own control plane; a plugin must never ask for it.
- Required permissions
All of:system_configuration.manage
Request body
application/json · Required:Yes
createStatusPageIncident Request body| Name | Type | Required | Description |
|---|
kind | string: incident / maintenance | Yes | — |
|---|
title | string | Yes | — |
|---|
impact | string | No | Required for an incident (degraded or outage); ignored for maintenance, which is always maintenance. |
|---|
status | string: investigating / identified / monitoring / resolved / scheduled / in_progress / completed | No | Incident: investigating, identified, monitoring or resolved (default investigating). Maintenance: scheduled, in_progress or completed (default scheduled). |
|---|
message | string | Yes | — |
|---|
component_ids | array<string(uuid)> | No | — |
|---|
scheduled_start | string(date-time) | No | Maintenance only, required there. |
|---|
scheduled_end | string(date-time) | No | Maintenance only, required there; after scheduled_start, at most 30 days after it, and in the future. |
|---|
Responses
createStatusPageIncident Responses| Status | Description |
|---|
201 | Created Fields:id: string(uuid) kind: string: incident / maintenance title: string impact: string: degraded / outage / maintenance status: string: investigating / identified / monitoring / resolved / scheduled / in_progress / completed component_ids: array<string(uuid)> scheduled_start?: string(date-time) scheduled_end?: string(date-time) started_at: string(date-time) resolved_at?: string(date-time) updates: array<IncidentUpdate> |
|---|
400 | Error |
|---|
401 | Error |
|---|
403 | Error |
|---|
503 | Error |
|---|
What to do on failure
400 Fix the parameters or body per the field list; do not retry unchanged.401 Check the credential format and whether it expired or was rotated.403 Check the key scopes, the owner’s current permissions and the tenant scope; never switch to a more privileged account.503 A dependency is unavailable: retry later with the original Idempotency-Key.
↑ Back to list
POST /v1/admin/status-page/incidents/{incident_id}/updates
Add an update to an incident
- operationId
addStatusPageIncidentUpdate- Auth
- Session: the Bearer session of a signed-in control plane user, used by the customer in their own control plane; a plugin must never ask for it.
- Required permissions
All of:system_configuration.manage
Parameters
addStatusPageIncidentUpdate Parameters| Name | In | Type | Required | Description |
|---|
incident_id | path | string(uuid) | Yes | — |
|---|
Request body
application/json · Required:Yes
addStatusPageIncidentUpdate Request body| Name | Type | Required | Description |
|---|
status | string: investigating / identified / monitoring / resolved / scheduled / in_progress / completed | Yes | Must belong to the incident's kind. |
|---|
message | string | Yes | — |
|---|
Responses
addStatusPageIncidentUpdate Responses| Status | Description |
|---|
200 | Updated incident Fields:id: string(uuid) kind: string: incident / maintenance title: string impact: string: degraded / outage / maintenance status: string: investigating / identified / monitoring / resolved / scheduled / in_progress / completed component_ids: array<string(uuid)> scheduled_start?: string(date-time) scheduled_end?: string(date-time) started_at: string(date-time) resolved_at?: string(date-time) updates: array<IncidentUpdate> |
|---|
400 | Error |
|---|
401 | Error |
|---|
403 | Error |
|---|
404 | Error |
|---|
409 | The incident is already resolved or the maintenance completed |
|---|
503 | Error |
|---|
What to do on failure
400 Fix the parameters or body per the field list; do not retry unchanged.401 Check the credential format and whether it expired or was rotated.403 Check the key scopes, the owner’s current permissions and the tenant scope; never switch to a more privileged account.404 The resource does not exist or belongs to another tenant.409 Read the current state first; a retry of the same operation keeps the original Idempotency-Key and body.503 A dependency is unavailable: retry later with the original Idempotency-Key.
↑ Back to list