> ## Documentation Index
> Fetch the complete documentation index at: https://docs.molesignal.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Set an incident's priority and urgency

> Change an incident's priority or urgency by hand.

```http theme={null}
PUT /api/v1/alerts/incidents/{id}/priority
PUT /api/v1/alerts/incidents/{id}/urgency
```

Both calls require `alerts.incidents.update` and take an active incident that was not merged into another; the
timeline records `priority_changed` and `urgency_changed`.

* **Priority**: the body is `{"priority": "P2"}`, or `null` for none: one of the organization's
  [priority levels](https://docs.molesignal.com/en-US/alerting/on-call.md#urgency-and-priority-levels). It changes the priority only and
  notifies nobody again.
* **Urgency**: the body names the key of one of the organization's urgency levels, such as
  `{"urgency": "high"}`, and the caller is recorded in `urgency_set_by`; support hours no longer change
  it. Raising an `open` incident to a more urgent level notifies again from the first step that applies,
  with `escalation.reason` `urgency_raised`; a less urgent level only changes the urgency, and a level
  that does not climb the steps stops further escalation.

To change many at once, use [bulk actions](https://docs.molesignal.com/en-US/api/alerting/bulk-incidents.md) with
`{"action": "set_priority", "priority": "P2"}` and `{"action": "set_urgency", "urgency": "low"}`.

```bash cURL theme={null}
curl -X PUT http://localhost:5080/api/v1/alerts/incidents/$INCIDENT_ID/urgency \
  -H "authorization: Bearer $MS_TOKEN" \
  -H "content-type: application/json" \
  -d '{"urgency": "high"}'
```

The response is the incident. Its `urgency` is the key of a level (incidents opened before the field
existed lack it and count as high), and `priority` is `P1` to `P9` or absent; `urgency_by_policy` is
`true` when the urgency came from the escalation policy.

**Errors**

| Status | Reason |
| - | - |
| `400` | The priority is beyond the organization's levels, or the urgency is not one of its levels. |
| `422` | The priority is not `P1` to `P9`, or the urgency is not a key of lowercase letters, digits, and underscores. |
| `403` | The token lacks `alerts.incidents.update`, or cannot access the incident. |
| `404` | No such incident. |
| `409` | The incident recovered or was merged into another. |


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.