Skip to main content
GET
Get post-mortem

Restrictions

Usage

  • Get post_mortem_id from POST /incident/post-mortem/list, or from an incident’s post_mortem_id.
  • Private post-mortems can be read only by account owners, admins, and members of the post-mortem’s team; others get AccessDenied.
  • An unknown post_mortem_id returns ResourceNotFound.

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.

Query Parameters

post_mortem_id
string
required

Post-mortem ID: a 32-character hex string derived from the account ID and the linked incident IDs.

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.