---
title: "Unpublish Postmortem"
description: "Takes a published postmortem off the status pages; the text stays as a draft."
---

`DELETE /api/incidents/:id/postmortem/publish`

Takes the postmortem of an incident off its status pages. The text is kept as a draft and can be published again with [Publish Postmortem](/api/monitoring/publish-postmortem). A `postmortem_published` notification that has not been delivered yet (subscription delay) is not sent.

## Authentication

Requires role `admin` or `editor` within the incident's customer scope. `readonly` gets `403 forbidden`.

- Header: `Authorization: Bearer <token>`

## Path Parameters

- `id` (required): numeric id or `publicId` (UUID) of the incident.

## Example (cURL)

```bash
curl -X DELETE "$BASE_URL/api/incidents/5121/postmortem/publish" \
  -H "Authorization: Bearer $TOKEN"
```

## Response

`204 No Content`, no body.

## Common Errors

- `401 Unauthorized` when not authenticated
- `403 Forbidden` (`forbidden`) when your role or customer scope does not allow it
- `404 Not Found` (`incidentNotFound`) when the incident does not exist in your organization
- `404 Not Found` (`postmortemNotFound`) when the incident has no published postmortem (also on a second call)