---
title: "Update Playbook Alert"
method: PUT
path: "/common/{playbook_alert_id}"
tags: ["Common"]
---

# Update Playbook Alert

`PUT /common/{playbook_alert_id}`

Update a Playbook Alert. Generic alert properties like status, priority and assignee may be updated, or a log message may be appended.

## Path parameters

- `playbook_alert_id` string, required

## Request body

- object
  - `priority` 'High' | 'Moderate' | 'Informational' — The priority of the Playbook Alert.
  - `status` 'New' | 'InProgress' | 'Dismissed' | 'Resolved' — The status of the Playbook Alert.
  - `assignee` string — ID of the assignee
  - `log_entry` string — Freetext log message. Maximum of 5000 characters.
  - `reopen` 'Never' | 'SignificantUpdates' — Reopen strategies can only be applied to alerts with a status of Dismissed or Resolved. The following combinations of status/reopen are allowed: * Dismissed -> Never * Resolved -> Never * Resolved -> SignificantUpdates
  - `added_actions_taken` OnwardActionId[]
  - `removed_actions_taken` OnwardActionId[]

## Response `200`

Result of the update request.

- PlaybookAlertStatusResponse
  - `status_code` 'Ok' | 'Error' — Status describing the result of the request.
  - `status_message` string — Text describing the status, suitable for displaying an error.

---

[API](https://skmtc.net/recordedfuture/apis/alert-api.md) · [All operations](https://skmtc.net/recordedfuture/apis/alert-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/recordedfuture/alert-api/revisions/c8c2f68d8b60/schema)