Skip to main content
POST
Delete event timeline entry

Restrictions

Usage

  • The latest timeline entry cannot be deleted; trying returns InvalidParameter.
  • After deletion, the event’s status, description, close time, and affected components are recomputed from the remaining entries.
  • Returns success when the event does not exist, and ResourceNotFound when the event exists but update_id does not.
  • 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 deleting a timeline entry on a status page event.

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

Timeline update ID to delete; obtain it from GET /status-page/change/info.

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.