---
title: "Undo your own false-alarm or non-threatening close"
method: POST
path: "/eval/operator/{event_id}/undo"
tags: ["eval"]
---

# Undo your own false-alarm or non-threatening close

`POST /eval/operator/{event_id}/undo`

## Request

- Base URL: `https://api.verdun.ai` (the document declares no server; this is the origin it was published from)
- URL: `https://api.verdun.ai/eval/operator/{event_id}/undo`
- Auth: HTTP bearer

Takes back the caller's own single-event FALSE_ALARM or SUSPICIOUS_MONITOR close within 10 seconds of it (database clock, plus a 2 s latency allowance): the evaluation and any training sample captured from it are deleted, the alarm returns to the queue, and the caller takes its claim. 404 when the event is unknown or has no close to undo (including a second undo), 403 out of scope, missing the review_label_alarms permission, or the close was made by another operator or the agent; 409 "Too late to undo this close" after the window, 409 "This close can't be undone" for an escalation, a bulk close, or an audited close.

## Path parameters

- `event_id` string, required

## Response `200`

Successful Response

- UndoOperatorEvalResponse
  - `event_id` string, required: The event whose close was taken back
  - `reopened` boolean, required: Always true on 200: the evaluation is gone, the alarm is back in the queue and claimed by the caller (unless their role never holds claims).

## Other responses

- `422`: Validation Error

---

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