Post-Mortems API: List and Retrieve Post-Mortem Reports

Post-mortems in Scrubbe are structured blameless reviews created automatically when an incident reaches the RESOLVED or CLOSED state. Each report captures the full incident timeline, identified root cause, contributing factors, follow-up action items, and lessons learned — ready to be integrated with external wikis, knowledge bases, or executive reporting pipelines. The Post-Mortems API currently provides a read interface over these records.

All endpoints require Authorization: Bearer <token>.

Base path: https://your-api-domain.com/api/v1/postmortems

List post-mortems

Returns a paginated list of post-mortem reports for the workspace, ordered by creation date descending. Each report is linked to its originating incident. GET /

number

default:"1"

Page number.

number

default:"20"

Items per page (max 100).

string

Filter to the post-mortem for a specific incident.

string

Start of the date range (ISO 8601).

string

End of the date range (ISO 8601).

GET /api/v1/postmortems?page=1&limit=10
Authorization: Bearer <token>

Response

{
  "success": true,
  "message": "Post-mortems retrieved",
  "data": [
    {
      "id": "PM-20260522-0007",
      "incidentId": "INC-20260519-0033",
      "incidentSummary": "Database primary failover — us-east-1",
      "severity": "HIGH",
      "resolvedAt": "2026-05-19T22:14:00Z",
      "duration": "1h 42m",
      "rootCause": "Disk saturation on primary node triggered unplanned failover",
      "timeline": [
        { "time": "2026-05-19T20:32:00Z", "event": "Alerting fired: disk usage > 95%" },
        { "time": "2026-05-19T20:45:00Z", "event": "On-call acknowledged alert" },
        { "time": "2026-05-19T22:14:00Z", "event": "Traffic re-routed to replica; service restored" }
      ],
      "contributingFactors": [
        "Log rotation job disabled during maintenance window",
        "Disk growth rate underestimated in capacity plan"
      ],
      "actionItems": [
        {
          "action": "Re-enable log rotation job",
          "owner": "platform@example.com",
          "dueDate": "2026-05-26T00:00:00Z"
        }
      ],
      "lessonsLearned": "Capacity alerts should fire at 80% to provide adequate response time.",
      "createdAt": "2026-05-20T08:00:00Z"
    }
  ],
  "meta": {
    "total": 23,
    "page": 1,
    "limit": 10,
    "totalPages": 3
  }
}

string

Unique post-mortem identifier.

string

ID of the originating incident.

string

Brief description of the incident.

string

Incident severity at time of resolution.

string

ISO 8601 timestamp when the incident was resolved.

string

Human-readable time from incident open to resolution.

string

The identified root cause of the incident.

object[]

Ordered list of significant events during the incident.

Show properties

string

ISO 8601 timestamp.

string

Description of the event.

string[]

Factors that amplified the incident’s impact or duration.

object[]

Follow-up tasks identified during the post-mortem review.

Show properties

string

Description of the required action.

string

Email of the responsible party.

string

ISO 8601 due date.

string

Key takeaways from the post-mortem review.

string

ISO 8601 timestamp when the post-mortem was generated.

Post-mortems are generated automatically when an incident is resolved. Use the Ezra AI endpoints to trigger deeper analysis and generate audience-specific reports from a post-mortem.

Overview

Incidents & Tickets

Intelligence

Operations

Platform

Post-Mortems API: List and Retrieve Post-Mortem Reports

List post-mortems

​List post-mortems

List post-mortems