Submit and materialize one exact saved campaign candidate

POST/v1/optimization-campaigns/{campaignId}/attempts/{attemptId}/candidate

Verifies producer, base, objective, and snapshot identities, then creates candidate-bound Test and Evaluation Runs without publication or deployment.

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
campaignIdpathstringYesDurable Optimization Campaign ID
attemptIdpathstringYesImmutable Optimization Campaign attempt ID
Query parameters
None.

Body schema

Content type: application/json · Required

FieldTypeRequiredDescription
proposalobjectYes—
proposal.schemaVersioncomputer_agents_optimization_candidate_v1Yes—
proposal.targetobjectYes—
proposal.target.kindfunction | metronomeYes—
proposal.target.resourceIdstringYes—
proposal.target.baseVersionIdstringYes—
proposal.target.baseFingerprintstringYes—
proposal.objectiveFingerprintstringYes—
proposal.candidateobjectYes—
proposal.candidate.fingerprintstringYes—
proposal.candidate.labelstringYes—
proposal.candidate.descriptionstringNoHuman-readable description.
proposal.candidate.snapshotobjectYes—
proposal.candidate.snapshot.namestringNoHuman-readable name.
proposal.candidate.snapshot.descriptionstringNoHuman-readable description.
proposal.candidate.snapshot.kindfunctionYes—
proposal.candidate.snapshot.sourceTypemanual | computer | gitNo—
proposal.candidate.snapshot.sourceEnvironmentIdstringNo—
proposal.candidate.snapshot.sourcePathstringNoWorkspace-relative file path.
proposal.candidate.snapshot.regionstringNo—
proposal.candidate.snapshot.runtimestringNo—
proposal.candidate.snapshot.authModepublic | privateNo—
proposal.candidate.snapshot.customDomainstringNo—
proposal.candidate.snapshot.metadataobjectNoVersionable Function metadata. Deployment identity and credentials are rejected.
proposal.candidate.snapshot.sourceFilesobject[]Yes—
proposal.candidate.snapshot.sourceFiles[].pathstringYesSafe relative versioned source path.
proposal.candidate.snapshot.sourceFiles[].namestringYesHuman-readable name.
proposal.candidate.snapshot.sourceFiles[].isFolderbooleanYes—
proposal.candidate.snapshot.sourceFiles[].sizeintegerYes—
proposal.candidate.snapshot.sourceFileContentsobjectYesComplete contents for every non-folder sourceFiles entry.
proposal.producerobjectYes—
proposal.producer.kindagent | human | deterministic | externalYes—
proposal.producer.idstringYesUnique identifier.
proposal.producer.versionIdstringNo—
proposal.producer.runIdstringNo—
proposal.evidenceobjectNo—
proposal.evidence.evaluationRunIdsstring[]No—
proposal.evidence.testRunIdsstring[]No—
proposal.evidence.assuranceRunIdsstring[]No—
proposal.evidence.repairEpisodeIdstringNo—
proposal.evidence.diagnosticFingerprintstringNo—
proposal.idempotencyKeystringYes—
producerCostUsdnumberNo—

What the API returns

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

202Candidate saved and evidence runs queued
None.
409Candidate or campaign provenance mismatch
None.
Submit and materialize one exact saved campaign candidate
Loading...
Response 202
Loading...
See the ACP quickstart and SDK flow