---
title: "Resolve an incident with a resolution summary"
method: POST
path: "/api/sre/incidents/{id}/resolve"
tags: ["AI SRE"]
---

# Resolve an incident with a resolution summary

`POST /api/sre/incidents/{id}/resolve`

## Request

- Base URL: `https://demo.supercheck.dev`
- URL: `https://demo.supercheck.dev/api/sre/incidents/{id}/resolve`
- Auth: HTTP bearer

## Path parameters

- `id` string, uuid, required

## Request body

- union: Send `resolutionSummary` (preferred) or the original `comment` field. The text is stored as the incident's resolution summary and recorded on the timeline.
  - object
    - `resolutionSummary` string, required
    - `comment` string: Original field name; equivalent to `resolutionSummary`.
  - object
    - `resolutionSummary` string
    - `comment` string, required: Original field name; equivalent to `resolutionSummary`.

## Response `200`

Incident resolved; timeline and audit events recorded, assignee and project notification channels notified

## Other responses

- `400`: Invalid ID or missing/oversized resolution summary
- `403`: Insufficient permission
- `404`: Incident not found in the active project

## Changes

- **2026-10-27** `4cc852288ddb`: 3 info
  - added the new optional request property `resolutionSummary`
  - added `subschema #1, subschema #2` to the request body `anyOf` list
  - the request property `comment` became optional
- **2026-10-01** `0114b54c259d`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/supercheck-io/apis/supercheck-api/changes/api/sre/incidents/:id/resolve/post.md)

---

[API](https://skmtc.dev/supercheck-io/apis/supercheck-api.md) - [All operations](https://skmtc.dev/supercheck-io/apis/supercheck-api/llms.txt) - [OpenAPI document](https://skmtc.dev/supercheck-io/apis/supercheck-api/revisions/7fa0162c07bd?raw)