Reconcile and accept a candidate against exact Assurance evidence
POST
/v1/optimization-campaigns/{campaignId}/attempts/{attemptId}/finalizeBinds the exact Assurance Run. A pending human approval remains waiting, failed Assurance rejects the candidate under campaign limits, and only trusted passed evidence produces an acceptance fingerprint.
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
| Name | Location | Type | Required | Description |
|---|---|---|---|---|
| campaignId | path | string | Yes | Durable Optimization Campaign ID |
| attemptId | path | string | Yes | Immutable Optimization Campaign attempt ID |
Query parameters
None.
Body schema
Content type: application/json · Required
| Field | Type | Required | Description |
|---|---|---|---|
| assuranceRunId | string | Yes | — |
What the API returns
Each response code below includes the documented payload shape for the ACP API.
200Waiting
None.
409Assurance is stale
None.
Reconcile and accept a candidate against exact Assurance evidence
Loading...
Response 200
Loading...