> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mithunai.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Draft a postmortem

> Ask the DevOps employee for a postmortem draft, which a person edits and approves.

The DevOps employee writes a draft from what is connected: a timeline, the impact, the likely cause
with how sure it is, the evidence and action items. The draft is a **proposal**: a person edits it
and approves it, and it is filed in Jira only when Jira is connected. Otherwise nothing is sent and
the console offers it to copy or download.

A resolved PagerDuty incident asks for one by itself ([PagerDuty webhook](https://docs.mithunai.com/api-reference/employees/receive-pagerduty-webhook.md)).
Use this for any other incident. It needs `agent.update`: Owner, Admin or Editor.

> [!WARNING]
>
> AI employees are in **beta**. This answers `404` unless your deployment has switched the beta on.
> Not yet run against a real account. See [DevOps](https://docs.mithunai.com/team/devops.md).

## Body

**service** `string` *required*

The service it was about. Letters, digits, dots, dashes and underscores.

**title** `string` *required*

What the incident was. At most 200 characters.

**reference** `string`

The alert's reference, as it was filed: `alert-...`, `sentry-...` or `pagerduty-...`. With a
`sentry-` or `pagerduty-` reference the draft reads that issue or incident, including PagerDuty's
timeline.

## Response

**results** `object[]` *required*

One item: `service`, `title`, `status` (`filed`, `repeat` or `over_limit`) and `task_id`.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.