# Update an Incident Update
Modifies existing Incident Update. Only modified attributes may be passed in payload. All other attributes will remain unchanged.
Endpoint: PUT /hubs/{subdomain}/incidents/{incident_id}/incident_updates/{incident_update_id}
Version: 3.0-R1
Security: ApiKeyAuth
## Path parameters:
- `subdomain` (string, required)
Unique subdomain of requested Hub.
- `incident_id` (integer, required)
id of the requested incident.
- `incident_update_id` (integer, required)
id of the requested incident update
## Query parameters:
- `api_version` (string)
Api version
Enum: "V3-R1"
## Request fields (application/json):
- `title` (string)
Title of this update. Can contain only plain text. Setting title to value different from current title of Incident may result in changing of Incident title. Incident title equals to title of latest (by start_time) published (not draft) Incident Update title.
- `start_time` (string,null)
Timestamp of event start. Can't be in future. ISO8601 formatted time (UTC).
Example: "2020-09-01T08:29:00Z"
- `incident_type` (string)
Type of Incident Update. Exact meaning may depend on use case and there is just one restriction: resolved can't be used as type of a first (by start_time) Incident Update.
Enum: "investigating", "identified", "monitoring", "resolved"
- `service_statuses` (array)
Describes affected services and their statuses. This parameter is forbidden if incident_type is resolved because resolving an incident automatically sets all affected services to up status for this incident.
- `service_statuses.service_id` (integer)
Example: 1234
- `service_statuses.status` (string)
Enum: "up", "degraded-performance", "down"
- `body` (string)
Example: "Message for an event or event update.
\nMay contain basic HTML tags.\n"
- `silent` (boolean)
When true notifications are not being sent to subscribers. Does not impact draft notifications for Team Members.
- `state` (string,null)
State of Incident or Incident Update:
* draft - Not published on Hub Page,
* unconfirmed - Published on Hub Page but marked as unconfirmed,
* published - Published on Hub Page.
Enum: "draft", "unconfirmed", "published"
## Response 200 fields (application/json):
- `id` (integer)
Example: 25
- `author` (string,null)
Author email
- `title` (string)
Title of this update. May be different from current incident title. Incident title may be changed during the duration of incident and therefore some updates may reflect previous title.
- `body` (string)
Example: "Message for an event or event update.
\nMay contain basic HTML tags.\n"
- `created_at` (string)
Timestamp of record creation. ISO8601 formatted time (UTC).
Example: "2020-09-01T08:29:00Z"
- `start_time` (string)
Timestamps of a Incident Update. ISO8601 formatted time (UTC).
Example: "2020-09-01T08:29:00Z"
- `updated_at` (string)
Timestamp of last modification of record. ISO8601 formatted time (UTC).
Example: "2020-09-01T08:29:00Z"
- `incident_type` (string)
Type of Incident Update. Exact meaning may depend on use case and there is just one restriction: resolved can't be used as type of a first (by start_time) Incident Update.
Enum: "investigating", "identified", "monitoring", "resolved"
- `state` (string,null)
State of Incident or Incident Update:
* draft - Not published on Hub Page,
* unconfirmed - Published on Hub Page but marked as unconfirmed,
* published - Published on Hub Page.
Enum: "draft", "unconfirmed", "published"
- `service_statuses` (array)
- `service_statuses.service_id` (integer)
Example: 62
- `service_statuses.service_name` (string)
- `service_statuses.status` (string)
Enum: "up", "degraded-performance", "down"
- `service_statuses.group_id` (integer)
Example: 63
- `service_statuses.group_name` (string)
- `service_statuses.flags` (object)
- `service_statuses.flags.deleted` (boolean)
- `service_statuses.flags.archived` (boolean)