Skip to main content
POST
Update post-mortem basics

Restrictions

Usage

  • Every call is recorded in the account audit log. Don’t put secrets in request fields.

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

Basic incident facts to write back to a post-mortem report.

post_mortem_id
string
required

Post-mortem ID.

incidents_highest_severity
string
required

Highest severity among linked incidents.

incidents_earliest_start_seconds
integer<int64>
required

Unix timestamp in seconds for the earliest linked incident start time.

Required range: x >= 1
incidents_latest_close_seconds
integer<int64>

Unix timestamp in seconds for the latest linked incident close time. 0 when still open.

Required range: x >= 0
incidents_total_duration_seconds
integer<int64>

Total incident duration in seconds.

Required range: x >= 0
responder_ids
integer<int64>[]

Responder member IDs to store on the report.

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

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