Record a managed producer failure
POST
/v1/optimization-campaigns/{campaignId}/attempts/{attemptId}/failureRecords bounded producer cost and an auditable failure classification, then either creates a fresh attempt or terminates the campaign under its immutable limits.
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 |
|---|---|---|---|
| classification | candidate_invalid | producer_unavailable | producer_failed | contract_invalid | Yes | — |
| error | string | Yes | — |
| retryable | boolean | Yes | — |
| costUsd | number | No | — |
What the API returns
Each response code below includes the documented payload shape for the ACP API.
200Producer failure recorded with retry or terminal action
None.
409Attempt is no longer producing
None.
Record a managed producer failure
Loading...
Response 200
Loading...