Skip to main content
POST
Update post-mortem basics

Restrictions

Usage

  • Requires the On-call Pro license.
  • The caller must be an account owner or admin, or a member of the report’s team; otherwise the call returns AccessDenied.
  • Full overwrite: omitted incidents_latest_close_seconds and incidents_total_duration_seconds become 0, and omitted responder_ids clears the responders.
  • IDs in responder_ids that do not resolve to a person are dropped; each stored responder gets the current time as assigned_at and acknowledged_at = 0.
  • 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

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

post_mortem_id
string
required

Post-mortem ID; obtain it from POST /incident/post-mortem/list.

incidents_highest_severity
enum<string>
required

Highest severity among the linked incidents.

  • Critical: critical.
  • Warning: warning.
  • Info: informational.
  • Ok: recovered.
Available options:
Critical,
Warning,
Info,
Ok
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>

Latest close time among the linked incidents, Unix timestamp in seconds. 0 (also when omitted) means still open.

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

Total incident duration in seconds; 0 when omitted.

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

Member IDs to store as the report's responders. Replaces the stored list; omit or send [] to clear it. IDs that do not resolve to a person are dropped.

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.