---
title: "Create audit finding"
method: POST
path: "/v1/findings"
tags: ["Findings"]
---

# Create audit finding

`POST /v1/findings`

Create an audit finding so teams can track issue ownership, remediation activity, severity, and supporting evidence.

## Request body

- CreateFindingDto
  - `taskId` string — Task ID
  - `evidenceSubmissionId` string — Evidence submission ID
  - `evidenceFormType` 'board-meeting' | 'it-leadership-meeting' | 'risk-committee-meeting' | 'meeting' | 'access-request' | 'whistleblower-report' | 'penetration-test' | 'rbac-matrix' | 'infrastructure-inventory' | 'employee-performance-evaluation' | 'network-diagram' | 'tabletop-exercise' — Evidence form type
  - `policyId` string — Policy ID
  - `vendorId` string — Vendor ID
  - `riskId` string — Risk ID
  - `memberId` string — Member ID (person this finding targets)
  - `deviceId` string — Device ID
  - `area` 'people' | 'documents' | 'compliance' | 'risks' | 'vendors' | 'policies' | 'other' — Broad area when the finding is not tied to a specific item
  - `type` 'soc2' | 'iso27001', required — Type of finding (SOC 2 or ISO 27001)
  - `severity` 'low' | 'medium' | 'high' | 'critical' — Severity
  - `content` string, required — Finding content/message

## Response `201`

---

[API](https://skmtc.net/om-network/apis/betayum-api.md) · [All operations](https://skmtc.net/om-network/apis/betayum-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/om-network/betayum-api/versions/1c5403653ecf/schema)