---
title: "Update an incident"
method: PUT
path: "/incident/{id}"
tags: ["incident"]
---

# Update an incident

`PUT /incident/{id}`

Acknowledge or resolve an incident

## Path parameters

- `id` string, required — The id of the Incident

## Request body

- object
  - `acknowledgedAt` string, date, nullable — The date the incident was acknowledged
  - `resolvedAt` string, date, nullable — The date the incident was resolved

## Response `200`

Update a monitor

- Incident
  - `id` number, required — The id of the incident
  - `startedAt` string, date, nullable, required — The date the incident started
  - `monitorId` number, nullable, required — The id of the monitor associated with the incident
  - `acknowledgedAt` string, date, nullable — The date the incident was acknowledged
  - `acknowledgedBy` number, nullable, required — The user who acknowledged the incident
  - `resolvedAt` string, date, nullable — The date the incident was resolved
  - `resolvedBy` number, nullable, required — The user who resolved the incident

## Other responses

- `400` — The server cannot or will not process the request due to something that is perceived to be a client error (e.g., malformed request syntax, invalid request message framing, or deceptive request routing).
- `401` — The client must authenticate itself to get the requested response.
- `402` — A higher pricing plan is required to access the resource.
- `403` — The client does not have the necessary permissions to access the resource.
- `404` — The server can't find the requested resource.
- `409` — The request could not be completed due to a conflict mainly due to unique constraints.
- `500` — The server has encountered a situation it doesn't know how to handle.

---

[API](https://skmtc.net/openstatus/apis/openstatus-api.md) · [All operations](https://skmtc.net/openstatus/apis/openstatus-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/openstatus/openstatus-api/revisions/f075fbb509f7/schema)