StatusDashboard
EventsPost-Mortem

Get post-mortem

Retrieve the post-mortem for an event.

View Markdown

GET /app/events/{id}/post-mortem

Returns the post-mortem for an event, or null if one has not been created yet. Requires the Post-Mortem Reports feature entitlement.

Post-mortems are only supported on incident and maintenance events. Requesting a post-mortem for an informational event returns 400.


Path parameters

ParameterDescription
idThe event ID.

Request

See API Basics for required headers.


Sample request

curl https://api.statusdashboard.com/app/events/4f8b2e1a-3c7d-4e9f-a0b1-c2d3e4f56789/post-mortem \
  -H "Authorization: Bearer bcf847abf5c6:def456"

Sample response

Status: 200 OK

{
  "postMortem": {
    "executiveSummary": "A misconfigured load balancer rule caused elevated API latency for approximately 45 minutes, affecting around 12% of requests.",
    "rootCauseAnalysis": "A deploy at 09:30 UTC introduced a load balancer rule with an incorrect timeout value. This caused upstream connections to be dropped under moderate load.",
    "actionItems": [
      {
        "id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
        "text": "Add load balancer config to pre-deploy validation checks.",
        "status": "done",
        "owner": "Platform team",
        "ownerIsPublic": true,
        "expectedCompletionAt": "2026-04-30",
        "completedAt": "2026-04-26",
        "completedBy": "user@example.com",
        "isPublic": true
      },
      {
        "id": "b2c3d4e5-f6a7-8901-bcde-f12345678901",
        "text": "Review timeout defaults across all gateway configurations.",
        "status": "in_progress",
        "owner": "Infrastructure",
        "ownerIsPublic": true,
        "expectedCompletionAt": "2026-05-15",
        "isPublic": true
      },
      {
        "id": "c3d4e5f6-a7b8-9012-cdef-234567890123",
        "text": "Internal audit follow-up.",
        "status": "open",
        "owner": "Security",
        "ownerIsPublic": false,
        "isPublic": false
      }
    ],
    "published": true,
    "createdAt": "2026-04-25T12:00:00.000Z",
    "updatedAt": "2026-04-26T14:05:00.000Z",
    "updatedBy": "user@example.com"
  }
}

Returns { "postMortem": null } if no post-mortem has been saved yet.


Response fields

FieldTypeDescription
postMortemobject | nullPost-mortem report, or null when none has been saved. When present, contains the fields below.

When postMortem is present:

FieldTypeDescription
postMortem.executiveSummarystringOpening overview of scope, impact, and outcome. Gives readers the key facts before the detailed analysis. Rich text field. See Rich text fields.
postMortem.rootCauseAnalysisstringDetailed explanation of the root cause and contributing factors. Rich text field. See Rich text fields.
postMortem.actionItemsarrayList of remediation tasks. See Action item fields.
postMortem.publishedbooleanWhether the post-mortem is visible on status dashboards.
postMortem.createdAtstringISO 8601 UTC timestamp of when the post-mortem was first saved.
postMortem.updatedAtstringISO 8601 UTC timestamp of the last update.
postMortem.updatedBystringEmail of the user who last saved the post-mortem.

Action item fields

FieldTypeDescription
idstringUnique action item ID (UUID).
textstringDescription of the task. Max 500 characters.
statusstringopen, in_progress, or done.
ownerstring | absentOptional owner or team name. Max 100 characters.
ownerIsPublicbooleanWhen false, owner is omitted from the public post-mortem page.
expectedCompletionAtstring | absentISO 8601 date string (YYYY-MM-DD). Optional expected completion date.
completedAtstring | absentISO 8601 date string (YYYY-MM-DD). Optional actual completion date.
completedBystring | absentEmail of the user who first set completedAt. Assigned by the server.
isPublicbooleanWhen false, the action item is omitted from the public post-mortem page.

Error responses

StatusWhen
400Event is an informational type — post-mortems are not supported.
403Insufficient permissions.
404Event not found.

On this page

We use cookies

We use essential cookies to keep the site working, and optional analytics cookies to understand how it's used. Read our Privacy Policy.