Skip to main content
POST
Create event timeline entry

Restrictions

Usage

  • at_seconds must not be earlier than the event’s latest timeline entry.
  • Component changes whose status equals the component’s current status are dropped from the stored entry.
  • Moving to resolved or completed requires every affected component to be operational; posting a non-terminal status on a closed event reopens it.
  • The event description is set to this entry’s description. If the event has notify_subscribers enabled, subscribers are notified about this entry.
  • Manually moving an auto-updating maintenance to ongoing or completed cancels the matching scheduled transition.
  • Pass draft_id to publish a stored draft whose change_id is this event; a draft can be published only once.
  • Every call is recorded in the account audit log. Don’t put secrets in request fields.

Authorizations

app_key
string
query
required

APP Key created in the Flashduty console under My → APP Key. Send it as the app_key query parameter or in the Fd-App-Key request header. Its effective access is the intersection of the key's permission scope and the creator's current role permissions. Keep it secret.

Body

application/json

Parameters for appending an update to a status page event timeline.

page_id
integer<int64>
required

Status page ID; obtain it from GET /status-page/list.

change_id
integer<int64>
required

Target change ID; obtain it from GET /status-page/change/list.

status
enum<string>
required

Event status after this update; must be valid for the event type. Pass the current status to post an update without a status change. When moving to resolved or completed, all affected components must be back to operational.

Available options:
investigating,
identified,
monitoring,
resolved,
scheduled,
ongoing,
completed
description
string
required

Update description (Markdown). Must not be empty.

at_seconds
integer<int64>

Update time in Unix seconds; must not be earlier than the event's latest timeline entry. Defaults to the current time when omitted or 0.

component_changes
object[]

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

draft_id
string

ID of a pending draft created by POST /status-page/draft/create whose change_id is this event; it is marked published when the update is stored. Omit when not publishing a draft.

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

Result of appending a timeline update to a status page event.