Skip to main content
POST
Create event timeline entry

Restrictions

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 appending an update to a status page event timeline.

page_id
integer<int64>
required

Status page ID.

change_id
integer<int64>
required

Target event ID.

status
enum<string>
required

New event status. Must match the event type. When the status transitions to resolved or completed, all referenced components must become operational.

Available options:
investigating,
identified,
monitoring,
resolved,
scheduled,
ongoing,
completed
at_seconds
integer<int64>

Update timestamp in unix seconds. Defaults to now when omitted.

description
string

Update description (Markdown). Required.

component_changes
object[]

Component status transitions applied by this update. Component IDs must be unique.

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 appending a timeline update to a status page event.