> Documentation index for AI agents: https://docs.pagerduty.com/llms.txt

# Create an Incident Review

`POST https://api.pagerduty.com/incidents/{id}/review`

Create an Incident Review for the specified Incident.

An Incident can have at most one 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 Incident Review follows the account's default template, which determines its sections.

When called with a User API token, the caller owns the new 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

- **api_key** (apiKey) — `Authorization` header. The API Key with format `Token token=<API_KEY>`

## Path parameters

| Name | Type | Required | Description |
|---|---|---|---|
| `id` | string | yes | The ID of the resource. |

## Header parameters

| Name | Type | Required | Description |
|---|---|---|---|
| `Accept` | string | yes | The `Accept` header is used as a versioning header. Default: `application/vnd.pagerduty+json;version=2`. |

## Request body (`application/json`) — required

| Field | Type | Required | Description |
|---|---|---|---|
| `title` | string | yes | The title of the Incident Review. Max length: 255. |
| `owner_user_id` | string |  | The ID of the User who should own the Incident Review. Only for account API keys, whose Incident Reviews would otherwise have no owner; with a User API token the caller is the owner, and naming anyone else is rejected with `400`. The User must belong to the account. Ignored unless the account has per-review permissions. |

Example: Request Example

```json
{
  "title": "Database outage review"
}
```

## Response 201

The Incident Review created.

### `application/json`

| Field | Type | Required | Description |
|---|---|---|---|
| `incident_review` | object | yes | An Incident Review is a structured, post-resolution record of what happened during an Incident. Each Incident has at most one Incident Review. |
| `incident_review.id` | string |  | The unique identifier of the Incident Review. Read-only. |
| `incident_review.incident_id` | string |  | The ID of the Incident this Incident Review describes. Read-only. |
| `incident_review.title` | string |  | The title of the Incident Review. |
| `incident_review.status` | string |  | The status of the Incident Review. Moving to `completed` is rejected while any required section is still unfilled. On accounts where completed Incident Reviews are read-only, a `completed` Incident Review cannot be changed until it is reopened by setting another status. One of: `started`, `in_review`, `completed`. |
| `incident_review.sections` | array of object |  | The sections of the Incident Review, ordered by `priority`. Read-only. |
| `incident_review.sections[].title` | string |  | The title of the section. Read-only. |
| `incident_review.sections[].content` | string \| null |  | The section's content, as [Tiptap](https://tiptap.dev/) editor JSON. `null` or empty for a section that has not been written or generated yet. |
| `incident_review.sections[].priority` | integer |  | The display order of the section within the Incident Review. Lower values sort first. Read-only. |
| `incident_review.sections[].required` | boolean |  | Whether this section must be filled in before the Incident Review can be moved to the `completed` status. Read-only. |
| `incident_review.sections[].completed_at` | string \| null (date-time) |  | The time the section was marked completed, or `null` if it has not been completed. Read-only. |
| `incident_review.generation_status` | string |  | Whether an AI draft is currently being generated for this Incident Review. While this is `generating`, section content is still being written and the Incident Review should be re-fetched to see the result. Read-only. One of: `idle`, `generating`. |
| `incident_review.ai_generated` | boolean |  | Whether this Incident Review has been through the AI draft flow. Read-only. |
| `incident_review.template_id` | string \| null |  | The ID of the template this Incident Review currently follows, or `null` if it does not follow one. Read-only. |
| `incident_review.has_events` | boolean |  | Whether the Incident Review has at least one event on its timeline. Read-only. |
| `incident_review.action_item_count` | integer |  | The total number of action items on this Incident Review. Read-only. |
| `incident_review.completed_action_item_count` | integer |  | The number of completed action items on this Incident Review. Read-only. |
| `incident_review.created_by` | string \| null |  | The ID of the User who created this Incident Review, or `null` if it was not created by a User. Read-only. |
| `incident_review.created_at` | string (date-time) |  | The time the Incident Review was created. Read-only. |
| `incident_review.updated_at` | string (date-time) |  | The time the Incident Review was last modified. Read-only. |
| `incident_review.completed_at` | string \| null (date-time) |  | The time the Incident Review was completed, or `null` if it has not been completed. Read-only. |

Example: Response Example

```json
{
  "incident_review": {
    "id": "AGOBAMKTT5Z3RO7CR7T2ZGSMJA",
    "incident_id": "P1234ABC",
    "title": "Database outage review",
    "status": "started",
    "sections": [
      {
        "title": "Summary",
        "content": null,
        "priority": 0,
        "required": true,
        "completed_at": null
      }
    ],
    "generation_status": "idle",
    "ai_generated": false,
    "template_id": "AGOBAMKTT5Z3RO7CR7T2ZGSMJA",
    "has_events": false,
    "action_item_count": 0,
    "completed_action_item_count": 0,
    "created_by": "PUSER123",
    "created_at": "2026-09-01T20:00:00Z",
    "updated_at": "2026-09-01T20:00:00Z",
    "completed_at": null
  }
}
```

## Response 400

Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work.

### `application/json`

| Field | Type | Required | Description |
|---|---|---|---|
| `error` | object |  |  |
| `error.code` | integer |  | Read-only. |
| `error.message` | string |  | Error message string. Read-only. |
| `error.errors` | array of string |  | Read-only. |

## Response 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.

### `application/json`

| Field | Type | Required | Description |
|---|---|---|---|
| `error` | object |  |  |
| `error.code` | integer |  | Read-only. |
| `error.message` | string |  | Error message string. Read-only. |
| `error.errors` | array of string |  | Read-only. |

## Response 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.

### `application/json`

| Field | Type | Required | Description |
|---|---|---|---|
| `error` | object |  |  |
| `error.code` | integer |  | Read-only. |
| `error.message` | string |  | Error message string. Read-only. |
| `error.errors` | array of string |  | Read-only. |

## Response 429

Too many requests have been made, the rate limit has been reached.

### `application/json`

| Field | Type | Required | Description |
|---|---|---|---|
| `error` | object |  |  |
| `error.code` | integer |  | Read-only. |
| `error.message` | string |  | Error message string. Read-only. |
| `error.errors` | array of string |  | Read-only. |

## Developer Agreement

Your access to and use of the PagerDuty Developer Services is governed by the [PagerDuty Developer Agreement](https://docs.pagerduty.com/developer/pagerduty-developer-agreement).