Skip to main content
POST
Create status page draft

Restrictions

Usage

  • The draft payload is stored verbatim (up to 64 KB); the console publish form reads it back to prefill the event.
  • A draft lives for 30 days and is consumed exactly once when the event is published.
  • Every call is recorded in the account audit log. Don’t put secrets in request fields.

Authorizations

app_key
string
query
required

App key issued from the Flashduty console under Account → APP Keys. Required on every public API call. Keep it secret — it grants the same access as the owning account.

Body

application/json

Parameters for storing a status page draft. The draft payload is stored verbatim; only the validated fields listed below are interpreted.

draft
object
required

Draft payload, stored verbatim, up to 64 KB serialized. Validated fields: page_id, type (incident or maintenance), name, message; optional change_id (append an update to an existing event when > 0), status, affected_components, and start_time/end_time (Unix epoch seconds, new maintenance only).

source
string

Opaque marker of the drafting origin, e.g. ai_sre:sess_xxx. Up to 64 characters.

Maximum string length: 64

Response

Success

Success response envelope. On every 2xx response, request_id identifies the call (also mirrored in the Flashcat-Request-Id header) and data holds the endpoint-specific payload. Failure responses use a different shape — see ErrorResponse.

request_id
string
required

Unique ID for this request. Mirrored in the Flashcat-Request-Id response header. Include it when reporting issues.

Example:

"01HK8XQE3Z7JM2NTFQ5YJ8P9R4"

data
object
required

Result of storing a status page draft.