Skip to main content
POST
Update event timeline entry

Restrictions

Usage

  • Only at_seconds and description can be edited; an entry’s status and component changes are fixed.
  • Pass at least one of at_seconds (greater than 0) or a non-empty description; otherwise the call returns InvalidParameter.
  • at_seconds must stay between the previous and next entries; editing the first entry also moves the event start time.
  • Editing the latest entry’s description also updates the event description. No subscriber notification is sent.
  • 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 updating an existing timeline entry on a status page event. At least one of at_seconds or description must be provided; omitted fields keep their current values.

page_id
integer<int64>
required

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

change_id
integer<int64>
required

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

update_id
string
required

Target timeline update ID; obtain it from GET /status-page/change/info.

at_seconds
integer<int64>

New update time in Unix seconds; must not be earlier than the previous entry or later than the next one. Omit or pass 0 to keep the current time.

description
string

New update description (Markdown). Omit or pass an empty string to keep the current text; editing the latest entry also updates the event description.

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

No payload. Depending on the operation, data is {} or omitted from the envelope; rely only on the HTTP 200 status and the absence of error.