---
title: "Update an incident update"
method: PUT
path: "/incidents/updates/{updateId}"
tags: ["Status page"]
---

# Update an incident update

`PUT /incidents/updates/{updateId}`

## Request

- Base URL: `https://api.pulsetic.com/api/public`
- URL: `https://api.pulsetic.com/api/public/incidents/updates/{updateId}`
- Auth: API key in header `Authorization`

Edits an existing update's status/message/date. If this update is the incident's most recent one, changing `status` here also updates the parent incident's status (e.g. to `resolved`). Verified subscribers are emailed. Requires a full-access API key.

## Path parameters

- `updateId` integer, required

## Request body

- StatusPageIncidentUpdateInput: Also used to resolve an incident: submit `status: resolved`. The incident and its full update history are kept, never deleted.
  - `status` 'exploring' | 'identified' | 'update' | 'resolved', required: Case-insensitive on input, stored lowercase. One of `exploring`, `identified`, `update`, `resolved`.
  - `message` string, required: Plain text. Newlines are preserved; Markdown/HTML is not rendered. Max 65000 characters.
  - `date` string: Optional. `Y-m-d H:i[:s]` (UTC) or `d/m/Y h:i A`. Omitted defaults to the current time.

## Response `200`

successful operation. `created_at` is a unix timestamp.

- StatusPageIncidentUpdate
  - `id` integer
  - `incident_id` integer
  - `status` 'exploring' | 'identified' | 'update' | 'resolved'
  - `message` string
  - `date` string, date-time
  - `created_at` string, date-time
  - `updated_at` string, date-time

---

[API](https://skmtc.dev/pulsetic/apis/pulsetic-api-implementation.md) · [All operations](https://skmtc.dev/pulsetic/apis/pulsetic-api-implementation/llms.txt) · [OpenAPI document](https://skmtc.dev/pulsetic/apis/pulsetic-api-implementation/revisions/8e0c010eb8ed?raw)