Skip to main content
POST
/
status-page
/
change
/
timeline
/
create
Create event timeline entry
curl --request POST \
  --url 'https://api.flashcat.cloud/status-page/change/timeline/create?app_key=' \
  --header 'Content-Type: application/json' \
  --data '
{
  "page_id": 5750613685214,
  "change_id": 5821693893131,
  "status": "identified",
  "description": "We have identified the root cause and are working on a fix.",
  "at_seconds": 1712003600,
  "component_changes": [
    {
      "component_id": "01KC3GAZ6ZJE40H55GM31RPWZE",
      "status": "partial_outage"
    }
  ]
}
'
{
  "request_id": "01HK8XQE3Z7JM2NTFQ5YJ8P9R4",
  "data": {
    "update_id": "01KP0311872NVYFRRQ82FWXAP4"
  }
}

Documentation Index

Fetch the complete documentation index at: https://docs.flashcat.cloud/llms.txt

Use this file to discover all available pages before exploring further.

Restrictions

AspectValue
Rate limits1,000 requests/minute; 50 requests/second per account
PermissionsStatus Pages Events Manage (on-call)

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.