---
title: "Update a finding (status transition rules apply)"
method: PATCH
path: "/v1/findings/{id}"
tags: ["Findings"]
---

# Update a finding (status transition rules apply)

`PATCH /v1/findings/{id}`

Update a finding (status transition rules apply) in Betayum. Create, review, update, and track audit findings, remediation activity, and finding history for an organization.

## Path parameters

- `id` string, required

## Request body

- UpdateFindingDto
  - `status` 'open' | 'ready_for_review' | 'needs_revision' | 'closed' — Finding status
  - `type` 'soc2' | 'iso27001' — Finding type
  - `severity` 'low' | 'medium' | 'high' | 'critical' — Severity
  - `content` string — Finding content/message
  - `revisionNote` object, nullable — Auditor note when requesting revision

## Response `200`

## Changes

- **2026-04-20** `6e22489e33cb` — 4 info
  - added the new optional request property `severity`
  - removed the non-success response with the status `401`
  - removed the non-success response with the status `403`
  - removed the non-success response with the status `404`
- **2026-03-05** `946edaa856a9` — 1 warning
  - deleted the `header` request parameter `X-Organization-Id`

[Change history](https://skmtc.dev/om-network/apis/betayum-api/changes/v1/findings/:id/patch.md)

---

[API](https://skmtc.dev/om-network/apis/betayum-api.md) · [All operations](https://skmtc.dev/om-network/apis/betayum-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/om-network/betayum-api/revisions/95679a9aa625/schema)