---
title: "Update alert priority"
method: PATCH
path: "/api/{cloudId}/v1/alerts/{id}/priority"
tags: ["Alerts"]
---

# Update alert priority

`PATCH /api/{cloudId}/v1/alerts/{id}/priority`

This endpoint is used to modify the priority level of an existing alert. This endpoint allows for dynamic control over alert urgency. This aids in effective incident management by ensuring the most critical issues are addressed first.

## Path parameters

- `id` string, required

## Request body

- UpdateAlertPriorityRequest
  - `priority` 'P1' | 'P2' | 'P3' | 'P4' | 'P5', required — Urgency level of the alert. The priority can be set as 'P1', 'P2', 'P3', 'P4', or 'P5', with 'P1' being the highest and 'P5' the lowest. The 'priority' attribute aids in effective alert management by allowing alerts to be categorized and handled according to their importance.

## Response `202`

Returned if the request is successful.

- SuccessResponse
  - `result` string — Indicates the outcome of the request.
  - `requestId` string — Identifier of the request. This ID can be used to trace or track the request in the system logs or for debugging purposes in case the request fails or causes an error.
  - `took` integer

## Other responses

- `401` — Returned if the authentication credentials are incorrect.
- `422` — Returned if the payload cannot be validated.

---

[API](https://skmtc.net/atlassian/apis/jsm-operations-api.md) · [All operations](https://skmtc.net/atlassian/apis/jsm-operations-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/atlassian/jsm-operations-api/versions/ed65f017bcb8/schema)