Hanzo AIDocs
Sign inAPI key

List findings

The org's findings — rule, severity, path, line, masked preview and fingerprint — newest first, across scans or within one.

GET /v1/security/findings

Security → · All API references → · Get started →

Addresshttps://api.hanzo.ai/v1/security/findings
MethodGET
Operationget_security_findings
AuthAuthorization: Bearer $HANZO_API_KEY

The org's findings — rule, severity, path, line, masked preview and fingerprint — newest first, across scans or within one.

A minSeverity outside critical|high|medium|low is refused rather than quietly ignored, so a filter typo cannot read as "no findings". Strictly org-scoped, and a caller with no validated org is refused.

Request

3 fields.

FieldInTypeRequiredDescription
scanIdquerystring—ScanID narrows to a single scan.
minSeverityquerystring—MinSeverity drops everything below that rank: critical, high, medium or low.
limitqueryinteger—Limit caps the page.

Response

StatusBodyMeaning
200security.findingListok
defaultproblem-detailsrefused

200 body — 11 fields.

FieldInTypeAlwaysDescription
databodysecurity.findingView[]—Data is the caller org's findings, newest first.
data[].createdAtbodyinteger (int64)—CreatedAt is when the finding was recorded, in Unix milliseconds.
data[].fingerprintbodystring—Fingerprint is the SHA-256 of the raw secret.
data[].idbodystring—ID addresses this finding.
data[].linebodyinteger (int64)—Line is where in that file.
data[].pathbodystring—Path is the file the secret was found in.
data[].previewbodystring—Preview is the secret MASKED — first and last characters kept, the middle starred — so a reviewer can recognise it without it being disclosed.
data[].ruleIdbodystring—RuleID is the detection rule that fired.
data[].ruleNamebodystring—RuleName is that rule's human name.
data[].scanIdbodystring—ScanID is the scan that produced it.
data[].severitybodystring—Severity ranks the finding: critical, high, medium or low.

Failure carries the platform error shape — see Errors.

Examples

hanzo security findings list
import { Configuration, SecurityApi } from 'hanzoai';

const api = new SecurityApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getSecurityFindings();
from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import SecurityApi

client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = SecurityApi(client).get_security_findings()
cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)

resp, _, err := client.SecurityAPI.GetSecurityFindings(context.Background()).Execute()
if err != nil {
	return err
}
use hanzo_client::apis::{configuration::Configuration, security_api};

let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();

let result = security_api::get_security_findings(&cfg, Default::default()).await?;
import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.SecurityApi;

ApiClient client = new ApiClient();
client.setBearerToken(System.getenv("HANZO_API_KEY"));

var result = new SecurityApi(client).getSecurityFindings();
curl https://api.hanzo.ai/v1/security/findings \
  -H "Authorization: Bearer $HANZO_API_KEY"

MCP reaches security through the security tool, which names its 7 operations with its own verbs — this one among them, under a name only MCP declares. describe explains any of them:

curl -X POST https://api.hanzo.ai/v1/mcp \
  -H "Content-Type: application/json" \
  -d '{
       "jsonrpc": "2.0",
       "id": 1,
       "method": "tools/call",
       "params": {
         "name": "describe",
         "arguments": {
           "op": "list_security_findings"
         }
       }
     }'

Security API · All Hanzo APIs · Interactive reference

Was this page useful?
PreviousGet findingsNextList health