Skip to main content
POST
Create a status page incident

Authorizations

Authorization
string
header
required

An sre_ak_* API key holding the api:admin scope (or api:config_read, which every write refuses with read_only_key).

Body

application/json
first_update
string
required

The opening note, 1 to 2000 characters. It becomes the first entry in the timeline, recorded under the phase the incident opens at.

title
string
required

The incident's heading, as customers read it, up to 200 characters.

component_ids
string[]

The components this incident affects, which is what the page colours. get_status_page answers the ids. An id this organization does not own, or one that has been archived off the page, refuses the whole call rather than being dropped from the list.

impact
string

The headline severity the page shows, and what it colours the named components with: none, minor, major, critical, maintenance. Defaults to minor. major, critical and maintenance also email this organization's notification recipients; none and minor are a line on the page and nothing more. maintenance marks planned work rather than a fault.

scheduled_for
string

When a maintenance window starts, as an ISO 8601 timestamp with an offset (2026-10-01T01:00:00Z). The page's form takes its own configured time zone; this argument does not, so the value is unambiguous whoever sends it.

scheduled_until
string

When that window ends, same format, and it has to be after scheduled_for.

status
string

The phase: investigating, identified, monitoring, resolved. Defaults to investigating, which is what the page's form opens on. Opening straight at resolved is allowed and stamps the resolution time.

Response

Created.