---
title: "Create an incident update"
method: POST
path: "/status_pages/{status_page_id}/incidents/{incident_id}/updates"
tags: ["Incidents"]
---

# Create an incident update

`POST /status_pages/{status_page_id}/incidents/{incident_id}/updates`

## Request

- Base URL: `https://app.honeybadger.io/v3`
- URL: `https://app.honeybadger.io/v3/status_pages/{status_page_id}/incidents/{incident_id}/updates`
- Auth: HTTP bearer
- TypeScript: <https://skmtc.dev/honeybadger/apis/honeybadger-api/docs/status_pages/:status_page_id/incidents/:incident_id/updates/post.ts> (a function with typed inputs; its response is checked against the schema)

Posts an update to an incident.

## Path parameters

- `status_page_id` string, required
- `incident_id` string, required

## Request body

- IncidentUpdateInput: The writable fields of an incident update. `status` and `severity` default to `investigating` and `problem_detected`. If neither `start_at` nor `start_now` is given, the update starts now.
  - `message` string: The update's prose
  - `status` 'maintenance_scheduled' | 'in_maintenance' | 'maintenance_complete' | 'investigating' | 'identified' | 'resolving' | 'monitoring' | 'resolved': An incident's status.
  - `severity` 'problem_detected' | 'degraded_performance' | 'partial_outage' | 'outage' | 'operational': An incident's severity.
  - `start_at` string, date-time: When the update takes effect. Only a scheduled_maintenance incident may set this in the future.
  - `start_now` boolean: Start the update immediately, ignoring `start_at`. An update that has already started is left as it is, so sending it again changes nothing.
  - `should_notify` boolean: Announce the update on the status page's connected accounts and email the status page's subscribers

## Response `201`

Update created

- object
  - `data` IncidentUpdate, required: An update to a status page incident. The incident's prose lives here, and its `current_status`, `current_severity` and `closed_at` are derived from its updates.
    - `id` string, required
    - `incident_id` string, required: ID of the incident
    - `message` string, nullable: The update's prose
    - `status` 'maintenance_scheduled' | 'in_maintenance' | 'maintenance_complete' | 'investigating' | 'identified' | 'resolving' | 'monitoring' | 'resolved', required: An incident's status.
    - `severity` 'problem_detected' | 'degraded_performance' | 'partial_outage' | 'outage' | 'operational', required: An incident's severity.
    - `start_at` string, date-time: When the update takes effect. A future time schedules it.
    - `should_notify` boolean, nullable: Whether the update is announced on the status page's connected accounts
    - `notified_at` string, date-time, nullable: When the announcement was sent
    - `created_at` string, date-time: When the update was posted
    - `updated_at` string, date-time: When the update was last changed
  - `meta` ResponseMeta
    - `request_id` string: Unique identifier for the request, for correlating with support

## Other responses

- `401`: The credential is missing, invalid, expired or revoked (`unauthorized`), or was sent in a way v3 doesn't accept (see the examples).
- `403`: The credential isn't allowed to do this. `error.code` says why. An account or project the credential doesn't cover is 404 `not_found`, not 403.
- `404`: Resource not found
- `422`: Validation error

---

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