Reconcile a Function release from authoritative deployment state

POST/v1/release-control/{releaseId}/reconcile

Reloads the target Function deployment history and immutable published version, then closes an interrupted release only when both carry the exact server-authored release and version bindings. Caller-supplied deployment identities are not accepted.

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
releaseIdpathstringYesRelease ID
Query parameters
None.

Body schema

Content type: application/json · Optional

None.

What the API returns

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

200Release deployment reconciliation resultapplication/json
FieldTypeRequiredDescription
releaseobjectYes—
release.idstringYesUnique identifier.
release.objectreleaseYes—
release.projectIdstringYesProject ID.
release.targetobjectYes—
release.target.kindfunction | metronomeYes—
release.target.resourceIdstringYes—
release.candidateobjectYes—
release.candidate.idstringYesUnique identifier.
release.candidate.versionIdstringYes—
release.candidate.fingerprintstringYes—
release.candidate.acceptanceFingerprintstringYes—
release.assuranceobjectYes—
release.assurance.runIdstringYes—
release.assurance.evidenceFingerprintstringYes—
release.assurance.decisionFingerprintstringYes—
release.actionpublish | publish_and_deployYes—
release.statusqueued | promoting | ready_for_deployment | deploying | released | failed | cancelledYesCurrent lifecycle status.
release.idempotencyKeystringYes—
release.requestFingerprintstringYes—
release.evidenceFingerprintstringYes—
release.revisionintegerYes—
release.deploymentobjectYes—
release.deployment.attemptIdstringYes—
release.deployment.idstringYesUnique identifier.
release.deployment.revisionstringYes—
release.deployment.startedAtstringYesISO 8601 timestamp.
release.deploymentRequestobjectYes—
release.deploymentRequest.methodPOSTYes—
release.deploymentRequest.pathstringYesWorkspace-relative file path.
release.deploymentRequest.bodyobjectYes—
release.deploymentRequest.body.versionIdstringYes—
release.deploymentRequest.body.releaseIdstringYes—
release.errorobjectYes—
release.error.codestringYes—
release.error.messagestringYesMessage text.
release.promotedAtstringYes—
release.completedAtstringYesISO 8601 timestamp.
release.createdAtstringYesISO 8601 timestamp.
release.updatedAtstringYesISO 8601 timestamp.
release.eventsobject[]No—
release.events[].sequenceintegerYes—
release.events[].idstringYesUnique identifier.
release.events[].typestringYes—
release.events[].actorUserIdstringYes—
release.events[].payloadobjectYes—
release.events[].createdAtstringYesISO 8601 timestamp.
reconciledbooleanYes—
deploymentobjectYes—
deployment.idstringYesUnique identifier.
deployment.revisionstringYes—
409No exact successful deployment is available to reconcile
None.
Reconcile a Function release from authoritative deployment state
Loading...
Response 200
Loading...
See the ACP quickstart and SDK flow