Skip to main content
POST
Initialize post-mortem

Restrictions

Usage

  • Links at most 10 incidents to one post-mortem report.
  • 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

Parameters for initializing a post-mortem report from incidents.

incident_ids
string[]
required

Incident IDs to link to the report. 1-10 incidents.

Required array length: 1 - 10 elements
template_id
string
required

Template ID used to initialize 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

Full post-mortem report including basics, content and follow-ups.