Get finding evidence and remediation history

GET/v1/security/findings/{findingId}

How to call this endpoint

Every ACP API request uses bearer authentication. The examples here show the actual request path, auth header, and body shape that the platform expects.

Path, query, and header parameters

These parameters control which ACP object the endpoint acts on and how the request is processed.

Path parameters
NameLocationTypeRequiredDescription
findingIdpathstringYesSecurity finding ID
Query parameters
None.
Header parameters
NameLocationTypeRequiredDescription
X-Computer-Agents-OrganizationheaderstringNoActive organization context. If omitted, the authenticated user's personal organization is used.

Body schema

This endpoint does not require a request body.

None.

What the API returns

Each response code below includes the documented payload shape for the ACP API.

200Security finding detailapplication/json
FieldTypeRequiredDescription
findingobjectYes—
finding.idstringYesUnique identifier.
finding.repositoryIdstringYes—
finding.repositoryFullNamestringNo—
finding.fingerprintstringYes—
finding.ruleIdstringNo—
finding.titlestringYesDisplay title.
finding.summarystringYes—
finding.narrativeSummarystringYesEvidence-grounded written interpretation of this finding. The canonical scanner description remains available in summary.
finding.severitycritical | high | medium | low | informationalYes—
finding.confidencenumberYes—
finding.exploitabilitystringNo—
finding.cwestring[]No—
finding.cvssnumberNo—
finding.statusopen | accepted | risk_accepted | false_positive | fixedYesCurrent lifecycle status.
finding.firstSeenRunIdstringNo—
finding.lastSeenRunIdstringNo—
finding.assignedToUserIdstringNo—
finding.resolutionReasonstringNo—
finding.resolutionExpiresAtstringNo—
finding.fixedAtstringNo—
finding.metadataobjectNoFree-form metadata object.
finding.occurrenceCountintegerYes—
finding.createdAtstringYesISO 8601 timestamp.
finding.updatedAtstringYesISO 8601 timestamp.
occurrencesobject[]Yes—
occurrences[].idstringNoUnique identifier.
occurrences[].runIdstringNo—
occurrences[].commitShastringNo—
occurrences[].locationsobject[]No—
occurrences[].evidenceobjectNo—
occurrences[].validationobjectNo—
occurrences[].provenanceobjectNo—
occurrences[].narrativeSummarystringNoWritten interpretation captured for this finding occurrence and run.
occurrences[].createdAtstringNoISO 8601 timestamp.
remediationsobject[]Yes—
remediations[].idstringYesUnique identifier.
remediations[].repositoryIdstringYes—
remediations[].findingIdstringNo—
remediations[].findingIdsstring[]Yes—
remediations[].runIdstringNo—
remediations[].statusproposed | validating | waiting_approval | approved | published | rejected | failed | cancelledYesCurrent lifecycle status.
remediations[].lifecyclequeued | generating | agent_running | pull_request_open | pull_request_closed | merged | verifying | fixed | deployed | verification_failed | failed | cancelledYes—
remediations[].patchDigeststringYes—
remediations[].validationobjectYes—
remediations[].approvedByUserIdstringNo—
remediations[].approvedAtstringNo—
remediations[].branchNamestringNo—
remediations[].pullRequestIdstringNo—
remediations[].pullRequestUrlstringNo—
remediations[].workerThreadIdstringNo—
remediations[].sourceShastringNo—
remediations[].metadataobjectYesFree-form metadata object.
remediations[].createdAtstringYesISO 8601 timestamp.
remediations[].updatedAtstringYesISO 8601 timestamp.
404Resource not foundapplication/json
FieldTypeRequiredDescription
errorstringNo—
Get finding evidence and remediation history
Loading...
Response 200
Loading...
See the ACP quickstart and SDK flow