---
title: "Update a status page incident"
method: PUT
path: "/status-page/incidents/{incidentId}"
tags: ["Status page"]
---

# Update a status page incident

`PUT /status-page/incidents/{incidentId}`

## Request

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

Only changes the incident's title. To resolve an incident (or otherwise change its status), add an incident update via POST /incidents/{incidentId}/incident-update with `status: resolved` - the incident and its update history are kept, not deleted. Requires a full-access API key.

## Path parameters

- `incidentId` integer, required

## Request body

- object
  - `title` string, required

## Response `200`

successful operation. `created_at`/`updated_at` are unix timestamps.

- StatusPageIncident
  - `id` integer
  - `title` string
  - `status_page_id` integer
  - `status` 'exploring' | 'identified' | 'update' | 'resolved': The incident's current status, taken from its most recent update: one of `exploring`, `identified`, `update`, `resolved`. Only `resolved` (exact lowercase) is treated as resolved.
  - `created_at` string, date-time
  - `updated_at` string, date-time
  - `updates` 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)