Skip to main content
POST
Initialize post-mortem

Restrictions

Usage

  • Requires the On-call Pro license.
  • The report ID is derived from the account and the sorted incident_ids; calling again with the same incidents returns the existing report unchanged.
  • Fails with InvalidParameter when any incident is already linked to a different post-mortem.
  • Team, channel and privacy are copied from the channel of the first incident loaded; an incident without a channel cannot start a report.
  • The title is the incident titles joined by , (at most 512 characters), or the template name when all titles are empty.
  • A new report starts as drafting with an empty body; its basics (severity, times, responders) are computed from the incidents.
  • Converted follow-ups of these incidents that are not yet bound to a report are bound to it.
  • 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 initializing a post-mortem report from incidents.

incident_ids
string[]
required

Incident IDs (MongoDB ObjectIDs) to link to the report, 1–10. All must exist in the account. The same set always maps to the same report.

Required array length: 1 - 10 elements
Pattern: ^[0-9a-fA-F]{24}$
template_id
string
required

Template ID from POST /incident/post-mortem/template/list, e.g. the built-in post_mortem_default_tmpl_en-us or post_mortem_default_tmpl_zh-cn, or a custom template ID.

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

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