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

# Update Playbook Alert

`PUT /common/{playbook_alert_id}`

## Request

- Base URL: `https://api.recordedfuture.com/playbook-alert`
- URL: `https://api.recordedfuture.com/playbook-alert/common/{playbook_alert_id}`
- Auth: one of:
  - API key in header `X-RFToken`
  - OAuth 2
    - Authorization code: `https://id.recordedfuture.com/authorize`
    - Token URL: `https://id.recordedfuture.com/token`

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.dev/recordedfuture/apis/recorded-future-playbook-alerts.md) - [All operations](https://skmtc.dev/recordedfuture/apis/recorded-future-playbook-alerts/llms.txt) - [OpenAPI document](https://skmtc.dev/recordedfuture/apis/recorded-future-playbook-alerts/revisions/604701d2ce52?raw)