Update event timeline entry

Update a timeline entry for a status page event.

POST /status-page/change/timeline/update

Update event timeline entry

cURL

curl --request POST \
  --url 'https://api.flashcat.cloud/status-page/change/timeline/update?app_key=' \
  --header 'Content-Type: application/json' \
  --data '
{
  "page_id": 5750613685214,
  "change_id": 5821693893131,
  "update_id": "01KP0311872NVYFRRQ82FWXAP4",
  "description": "Corrected description: root cause identified in database layer.",
  "at_seconds": 1712003600
}
'

200

{
  "request_id": "01HK8XQE3Z7JM2NTFQ5YJ8P9R4",
  "data": {}
}

Restrictions

Aspect	Value
Rate limits	1,000 requests/minute; 50 requests/second per account
Permissions	Status 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 updating an existing timeline entry on a status page event.

page_id · integer<int64> · required

Status page ID.

change_id · integer<int64> · required

Parent event ID.

update_id · string · required

Target timeline update ID.

at_seconds · integer<int64>

New update timestamp in unix seconds.

description · string

New update description (Markdown).

Response

200

application/json

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

Empty response body. The server returns data: null on success.