|docs
Start Trial

For AI agents and assistants: visit https://docs.pagerduty.com/llms.txt for the index.

Create a Post-Incident Review

Create a Post-Incident Review for the specified Incident.

An Incident can have at most one Post-Incident Review, so this returns 400 if the Incident already has one. A caller that wants create-or-fetch behaviour should fall back to GET on failure.

The new Post-Incident Review follows the account's default template, which determines its sections.

When called with a User API token, the caller owns the new Post-Incident Review. An account API key may name an owner with owner_user_id.

Returns 400 if owner_user_id is not a User on the account, or if a User API token names someone other than the caller.

Scoped OAuth requires: incident_reviews.write

Authorization<token>

The API Key with format Token token=<API_KEY>

In: header

Path Parameters

id*string

The ID of the resource.

Header Parameters

Accept*string

The Accept header is used as a versioning header.

Default"application/vnd.pagerduty+json;version=2"

Request Body

application/json

TypeScript Definitions

Use the request body type in TypeScript.

Response Body

application/json

application/json

application/json

application/json

application/json

Developer Agreement

Your access to and use of the PagerDuty Developer Services is governed by the PagerDuty Developer Agreement.