What you can do
The API gives you access to your post-mortem documents and their metadata. Here’s what’s available:List and find post-mortems
You can list all post-mortems across your organization, or filter to find the post-mortems attached to a specific incident. This is useful for building dashboards, generating reports, or syncing post-mortem data with an internal tool.Fetch document metadata
Each post-mortem exposes metadata about the document: its status, the incident it belongs to, when it was created and last updated, and who has edited it. If you want to track post-mortem engagement (who’s writing them, who’s reviewing them, how quickly they’re being completed), this is where that data lives. Use the show endpoint to fetch the full details of a specific document.Fetch content as Markdown
You can fetch the full content of a post-mortem as Markdown. This is the same content you see in the editor, rendered as plain Markdown text. This is really powerful if you want to do something with the content that we don’t support natively. Maybe you want to feed post-mortems into an internal search engine, publish them to an internal wiki that we don’t integrate with, or run your own analysis across all your post-mortems. The content is right there, in a format that’s easy to work with. This is the same output you get when using “Copy as Markdown” from the editor’s overflow menu.Update status
You can update the status of a post-mortem programmatically. Move it from In Progress to In Review, or from In Review to Complete, without anyone having to open the UI. This is useful if you have an external review process (say, a pull request workflow or an approval system) and you want to update the post-mortem status when that process completes.Webhooks
We also support a webhook that fires every time a post-mortem’s status changes. The webhook payload includes the post-mortem metadata and the new status. This is the other side of the automation coin. Where the API lets you pull data and take actions, webhooks let you react to changes as they happen. Some things people use this for:- Trigger a notification in a tool we don’t have a native integration with (internal chat tool, email system, ticketing system).
- Update an external tracker when a post-mortem is completed, so your compliance or audit system knows that the post-incident process was followed.
- Kick off a custom pipeline that processes the post-mortem content. For example, extracting key metrics, updating a reliability scorecard, or feeding the content into an internal knowledge base.
postmortem_document_ids in incident responses, so you can discover which post-mortem documents are associated with each incident.