---
title: "Create or Update a Post Postmortem"
method: PUT
path: "/status_pages/{id}/posts/{post_id}/postmortem"
tags: ["Status Pages"]
---

# Create or Update a Post Postmortem

`PUT /status_pages/{id}/posts/{post_id}/postmortem`

Create or Update a Postmortem for a Post by Post ID.

Scoped OAuth requires: `status_pages.write`

## Path parameters

- `id` string, required
- `post_id` string, required

## Headers

- `Accept` string, required

## Request body

- object
  - `postmortem` StatusPagePostmortemRequest, required — Request to create/update a given Postmortem resource.
    - `type` 'status_page_post_postmortem', required — The type of the object returned by the API - in this case, a Status Page Post Postmortem.
    - `post` object, required — Status Page Post
      - `id` string, required — Status page post unique identifier
      - `type` string — A string that determines the schema of the object.
    - `message` string, required — The message of the Postmortem (supports Rich-Text).
    - `notify_subscribers` boolean, required — Whether or not subscribers of the Status Page should be notified about the Postmortem.

## Response `200`

OK

- object
  - `postmortem` StatusPagePostmortem — A Postmortem represents a communication resource presented in the Status Page about follow-up made to a certain Post.
    - `id` string — An unique identifier within Status Page scope that defines a single Postmortem resource.
    - `self` string — The API resource URL of the Postmortem.
    - `post` object — Status Page Post
      - `id` string, required — The id of the status page post.
      - `type` string — A string that determines the schema of the object.
    - `message` string — The message of the Postmortem (supports Rich-Text).
    - `notify_subscribers` boolean — Whether or not subscribers of the Status Page should be notified about the Postmortem.
    - `reported_at` string, date-time — The date and time the Postmortem was reported.
    - `type` string — The type of the object returned by the API - in this case, a Status Page Post Postmortem.

## Other responses

- `201` — Created
- `400` — Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work.
- `401` — Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed.
- `403` — Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action.
- `404` — The requested resource was not found.
- `429` — Too many requests have been made, the rate limit has been reached.

---

[API](https://skmtc.dev/pagerduty/apis/rest-api.md) · [All operations](https://skmtc.dev/pagerduty/apis/rest-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/pagerduty/rest-api/revisions/b679a8f3f02c/schema)