Persist a terminal remediation worker failure

POST/v1/security/remediations/{remediationId}/fail

Internal fenced worker endpoint.

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
remediationIdpathstringYes
Query parameters
None.
Header parameters
NameLocationTypeRequiredDescription
X-Computer-Agents-OrganizationheaderstringNoActive organization context. If omitted, the authenticated user's personal organization is used.

Body schema

Content type: application/json · Required

FieldTypeRequiredDescription
dispatchIdstringYes
codestringYes
messagestringYesMessage text.

What the API returns

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

200Failed remediationapplication/json
FieldTypeRequiredDescription
idstringYesUnique identifier.
repositoryIdstringYes
findingIdstringNo
findingIdsstring[]Yes
runIdstringNo
statusproposed | validating | waiting_approval | approved | published | rejected | failed | cancelledYesCurrent lifecycle status.
lifecyclequeued | generating | agent_running | pull_request_open | pull_request_closed | merged | verifying | fixed | deployed | verification_failed | failed | cancelledYes
patchDigeststringYes
validationobjectYes
approvedByUserIdstringNo
approvedAtstringNo
branchNamestringNo
pullRequestIdstringNo
pullRequestUrlstringNo
workerThreadIdstringNo
sourceShastringNo
metadataobjectYesFree-form metadata object.
createdAtstringYesISO 8601 timestamp.
updatedAtstringYesISO 8601 timestamp.
404Resource not foundapplication/json
FieldTypeRequiredDescription
errorstringNo
Persist a terminal remediation worker failure
Loading...
Response 200
Loading...
See the ACP quickstart and SDK flow