---
title: "Assign, schedule, acknowledge, accept the risk, or close a finding"
method: PATCH
path: "/v1/findings/{findingId}"
tags: ["Findings"]
---

# Assign, schedule, acknowledge, accept the risk, or close a finding

`PATCH /v1/findings/{findingId}`

## Request

- Base URL: `https://api.ironfang.com/audit`
- URL: `https://api.ironfang.com/audit/v1/findings/{findingId}`
- Auth: one of:
  - HTTP bearer
  - HTTP bearer

A person cannot mark a finding fixed: that is a claim about the page which only a passing observation can make, so closing one by hand needs a resolution such as false_positive or accepted_risk. Reopening is likewise something an observation does. Every change is recorded against the person who made it.

## Request body

- object
  - `accepted_risk_until` string: RFC 3339. When it passes, the finding stops being suppressed and notifies again.
  - `assignee_user_id` string: Empty string clears the assignment
  - `comment` string
  - `due_at` string: RFC 3339, or an empty string to clear
  - `resolution_code` 'false_positive' | 'accepted_risk' | 'superseded' | 'other'
  - `state` 'acknowledged' | 'accepted_risk' | 'resolved'

## Response `200`

The updated finding

## Other responses

- `404`: Problem response
- `422`: Problem response

---

[API](https://skmtc.dev/ironfang/apis/ironfang-audit-api.md) · [All operations](https://skmtc.dev/ironfang/apis/ironfang-audit-api/llms.txt) · [OpenAPI document](https://skmtc.dev/ironfang/apis/ironfang-audit-api/revisions/7430deff2cbd?raw)