Request security-run cancellation

POST/v1/security/runs/{runId}/cancel

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
runIdpathstringYesSecurity run 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.

200Updated runapplication/json
FieldTypeRequiredDescription
idstringYesUnique identifier.
repositoryIdstringYes
repositoryFullNamestringNo
triggerTypemanual | schedule | pull_request | push | retryYes
triggerEventIdstringNo
baseShastringNo
headShastringNo
refstringNo
statusqueued | running | waiting_approval | succeeded | partial | failed | cancelledYesCurrent lifecycle status.
stageingest | checkout | inventory | scan | validate | triage | remediate | verify | publish | completeYes
policyVersionIdstringNo
threatModelVersionIdstringNo
promptVersionstringNo
modelVersionstringNo
scannerVersionsobjectNo
coverageobjectNo
summaryobjectNo
errorobjectNo
findingCountintegerYes
checkRunUrlstringNo
pullRequestUrlstringNo
queuedAtstringYes
startedAtstringNoISO 8601 timestamp.
completedAtstringNoISO 8601 timestamp.
createdAtstringYesISO 8601 timestamp.
updatedAtstringYesISO 8601 timestamp.
404Resource not foundapplication/json
FieldTypeRequiredDescription
errorstringNo
Request security-run cancellation
Loading...
Response 200
Loading...
See the ACP quickstart and SDK flow