Skip to main content
POST
Update status page event

Restrictions

Usage

  • Status, description, and component impact cannot be changed here; post a timeline entry with POST /status-page/change/timeline/create instead.
  • An omitted or empty responders or linked_changes keeps the current list, so these lists cannot be cleared through this endpoint.
  • 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 the editable fields of a status page event.

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.

title
string | null

New event title, up to 255 characters. Omit to keep the existing value.

Maximum string length: 255
responders
integer<int64>[]

Member IDs responsible for this event, replacing the current list. An omitted or empty array keeps the current list.

linked_changes
string[]

Linked event IDs, replacing the current list. An omitted or empty array keeps the current list.

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.