> ## Documentation Index
> Fetch the complete documentation index at: https://docs.scrubbe.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Post-Mortems API: List and Retrieve Post-Mortem Reports
> Access structured post-mortem reports auto-generated from resolved incidents, covering root cause, contributing factors, and action items.
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 `.
**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 /`
Page number.
Items per page (max 100).
Filter to the post-mortem for a specific incident.
Start of the date range (ISO 8601).
End of the date range (ISO 8601).
```http theme={null}
GET /api/v1/postmortems?page=1&limit=10
Authorization: Bearer
```
**Response**
```json theme={null}
{
"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
}
}
```
Unique post-mortem identifier.
ID of the originating incident.
Brief description of the incident.
Incident severity at time of resolution.
ISO 8601 timestamp when the incident was resolved.
Human-readable time from incident open to resolution.
The identified root cause of the incident.
Ordered list of significant events during the incident.
ISO 8601 timestamp.
Description of the event.
Factors that amplified the incident's impact or duration.
Follow-up tasks identified during the post-mortem review.
Description of the required action.
Email of the responsible party.
ISO 8601 due date.
Key takeaways from the post-mortem review.
ISO 8601 timestamp when the post-mortem was generated.
Post-mortems are generated automatically when an incident is resolved. Use the [Ezra AI](/api-reference/ezra) endpoints to trigger deeper analysis and generate audience-specific reports from a post-mortem.