Execute a dispatched security run

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

Internal fenced worker endpoint. The caller must present the short-lived dispatch attestation bound to this exact security run and attempt.

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.

200Security execution result and refreshed run stateapplication/json
FieldTypeRequiredDescription
executionobjectYes
runobjectYes
run.idstringYesUnique identifier.
run.repositoryIdstringYes
run.repositoryFullNamestringNo
run.triggerTypemanual | schedule | pull_request | push | retryYes
run.triggerEventIdstringNo
run.baseShastringNo
run.headShastringNo
run.refstringNo
run.statusqueued | running | waiting_approval | succeeded | partial | failed | cancelledYesCurrent lifecycle status.
run.stageingest | checkout | inventory | scan | validate | triage | remediate | verify | publish | completeYes
run.policyVersionIdstringNo
run.threatModelVersionIdstringNo
run.promptVersionstringNo
run.modelVersionstringNo
run.scannerVersionsobjectNo
run.coverageobjectNo
run.summaryobjectNo
run.narrativeSummarystringYesEvidence-grounded written assessment of the run. New runs retain model and prompt provenance in summary.narrative; legacy runs receive a deterministic projection.
run.errorobjectNo
run.findingCountintegerYes
run.checkRunUrlstringNo
run.pullRequestUrlstringNo
run.queuedAtstringYes
run.startedAtstringNoISO 8601 timestamp.
run.completedAtstringNoISO 8601 timestamp.
run.createdAtstringYesISO 8601 timestamp.
run.updatedAtstringYesISO 8601 timestamp.
404Resource not foundapplication/json
FieldTypeRequiredDescription
errorstringNo
Execute a dispatched security run
Loading...
Response 200
Loading...
See the ACP quickstart and SDK flow