---
title: "Update Finding Status"
method: POST
path: "/v1/findings/{finding_id}/status"
tags: ["Findings"]
---

# Update Finding Status

`POST /v1/findings/{finding_id}/status`

## Request

- Base URL: `https://api.mindfort.app`
- URL: `https://api.mindfort.app/v1/findings/{finding_id}/status`
- Auth: HTTP bearer

Update a finding to ACTIVE, RESOLVED, or ARCHIVED to track remediation progress across your organization.

## Path parameters

- `finding_id` string, uuid, required

## Request body

- UpdateFindingStatusRequest
  - `status` 'ACTIVE' | 'RESOLVED' | 'ARCHIVED', required: New finding status
  - `resolve_reason` 'FIX' | 'WONT_FIX' | 'FALSE_POSITIVE' | 'null', nullable: Resolution reason. FALSE_POSITIVE is only valid when status is ARCHIVED and requires resolve_context.
  - `resolve_context` string, nullable: Optional resolution context. Required when archiving a FALSE_POSITIVE.

## Response `200`

Finding status updated successfully

- PublicSingleFindingStatusResult
  - `finding_id` string, uuid, required
  - `status` 'ACTIVE' | 'RESOLVED' | 'ARCHIVED', required
  - `updated` boolean, required

## Other responses

- `400`: Invalid finding_id, request body, or status
- `401`: Unauthorized – missing or invalid API key
- `404`: Finding not found
- `429`: Rate limit exceeded
- `500`: Internal server error

---

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