---
title: "Reopen threat"
method: POST
path: "/threatmonitoring/threat/reopen"
tags: ["threatmonitoring"]
---

# Reopen threat

`POST /threatmonitoring/threat/reopen`

## Request

- Base URL: `https://cyber-risk.upguard.com/api/public`
- URL: `https://cyber-risk.upguard.com/api/public/threatmonitoring/threat/reopen`
- Auth: API key in header `Authorization`
- TypeScript: <https://skmtc.dev/upguard/apis/upguard-cyberrisk-api/docs/threatmonitoring/threat/reopen/post.ts> (a function with typed inputs; its response is checked against the schema)

Reopens a closed threat, identified by UUID, and places it back into the investigating state.
The user identified by `investigator_email` is assigned as the investigator; they must belong
to your organization and have write permission for Threat Monitoring.

The threat can only be reopened if:
it is currently closed; and
it is not linked to a remediation request.

Required API key permissions: `BreachRisk` (select when creating API key in Account Settings)

## Query parameters

- `uuid` string, uuid, required
- `investigator_email` string, required

## Response `200`

The reopened threat

- ReopenThreatV1ResponsePayloadBody
  - `status` string: The status of the threat after reopening
  - `uuid` string: The UUID of the threat that was reopened

## Other responses

- `404`: There was a problem with the request
- `422`: An invalid parameter was supplied or a mandatory parameter was missing
- `429`: Too many requests have been made to this endpoint.
- `500`: An internal system error occurred

## Changes

- **2026-11-07** `d044bf6dc61e`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/upguard/apis/upguard-cyberrisk-api/changes/threatmonitoring/threat/reopen/post.md)

---

[API](https://skmtc.dev/upguard/apis/upguard-cyberrisk-api.md) - [All operations](https://skmtc.dev/upguard/apis/upguard-cyberrisk-api/llms.txt) - [OpenAPI document](https://skmtc.dev/upguard/apis/upguard-cyberrisk-api/revisions/d044bf6dc61e?raw)