> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mindfort.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Update Finding Status

> Update the workflow status of a red-team finding to ACTIVE, RESOLVED, or ARCHIVED to track its remediation progress across your organization.



## OpenAPI

````yaml /openapi.json post /v1/findings/{finding_id}/status
openapi: 3.1.0
info:
  title: MindFort API
  version: 1.0.0
  description: >-
    The MindFort Public API allows you to programmatically trigger assessments
    and tasks, browse targets and findings, and manage finding triage state.
    Authenticate using a Bearer API key generated from the MindFort dashboard.
servers:
  - url: https://api.mindfort.app
    description: Production
security:
  - bearerAuth: []
paths:
  /v1/findings/{finding_id}/status:
    post:
      tags:
        - Findings
      summary: Update Finding Status
      description: >-
        Update the workflow status of a red-team finding to ACTIVE, RESOLVED, or
        ARCHIVED to track its remediation progress across your organization.
      operationId: updateFindingStatus
      parameters:
        - name: finding_id
          in: path
          required: true
          description: UUID of the finding
          schema:
            type: string
            format: uuid
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/UpdateFindingStatusRequest'
      responses:
        '200':
          description: Finding status updated successfully
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/UpdateFindingStatusResponse'
        '400':
          description: Invalid finding_id, request body, or status
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '401':
          description: Unauthorized – missing or invalid API key
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '404':
          description: Finding not found
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '429':
          description: Rate limit exceeded
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '500':
          description: Internal server error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
components:
  schemas:
    UpdateFindingStatusRequest:
      type: object
      required:
        - status
      properties:
        status:
          type: string
          enum:
            - ACTIVE
            - RESOLVED
            - ARCHIVED
          description: New finding workflow status
    UpdateFindingStatusResponse:
      type: object
      properties:
        finding_id:
          type: string
          format: uuid
          description: UUID of the updated finding
        status:
          type: string
          enum:
            - ACTIVE
            - RESOLVED
            - ARCHIVED
          description: Updated finding workflow status
        updated:
          type: boolean
          description: Whether the update succeeded
    ErrorResponse:
      type: object
      properties:
        error:
          type: string
          description: Human-readable error message
        request_id:
          type: string
          description: Unique request identifier for debugging
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      description: >-
        API key generated from the MindFort dashboard. Pass as `Authorization:
        Bearer <your-api-key>`.

````