Skip to main content
GET
/
v1
/
findings
/
{finding_id}
Get Finding
curl --request GET \
  --url https://api.mindfort.app/v1/findings/{finding_id} \
  --header 'Authorization: Bearer <token>'
{
  "id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "title": "<string>",
  "severity": "critical",
  "severity_score": 123,
  "status": "ACTIVE",
  "created_at": "2023-11-07T05:31:56Z",
  "target_id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "description": "<string>",
  "impact": "<string>",
  "evidence": "<string>",
  "approach": "<string>",
  "remediation_advice": "<string>"
}

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.

Authorizations

​
Authorization
string
header
required

API key generated from the MindFort dashboard. Pass as Authorization: Bearer <your-api-key>.

Path Parameters

​
finding_id
string<uuid>
required

UUID of the finding

Response

Finding returned successfully

Full active finding details returned by the get finding endpoint.

​
id
string<uuid>

UUID of the finding

​
title
string | null

Finding title

​
severity
enum<string> | null

Finding severity

Available options:
critical,
high,
medium,
low,
info,
null
​
severity_score
number | null

Numeric severity score

​
status
enum<string>

Finding workflow status

Available options:
ACTIVE,
RESOLVED,
ARCHIVED
​
created_at
string<date-time>

Finding creation timestamp

​
target_id
string<uuid>

UUID of the target this finding belongs to

​
description
string | null

Finding description

​
impact
string | null

Potential security impact

​
evidence
string | null

Evidence collected during testing

​
approach
string | null

Testing approach used to validate the finding

​
remediation_advice
string | null

Recommended remediation guidance