Release a mapping to production
Release one eligible reviewed candidate. This is the only follow-up action that may activate a mapping and advance its mapping revision.
POST/v1/item-mapping-requests/{operation_reference}/production-releases
Request schema: SingleItemProductionReleaseRequestV1
Success schema: SingleItemProductionReleaseResponseV1
Documented HTTP statuses: 200, 400, 401, 403, 404, 409, 429, 503
Contract: v1-baseline.json
Authorization
Release requires its exact permission and fresh validation of company, application or delegation when applicable, entitlement, candidate eligibility, and both revisions.
Request guidance
Send the opaque candidate_token, current result_revision, and expected_mapping_revision. Stale or ineligible requests fail closed.
Parameters
| Name | In | Type | Presence | Constraints | Description |
|---|---|---|---|---|---|
operation_reference | path | string | Required |
Request fields
| Field | Type | Presence | Constraints |
|---|---|---|---|
candidate_token | string | Required | maximum 64 characters |
result_revision | integer or string (int64) | Required | minimum 1; maximum 3 |
expected_mapping_revision | integer or string (int64) | Required | minimum 0; maximum 9223372036854775806 |
Request example
No synthetic example is approved for this operation. Follow the request-field table and versioned schema.
Idempotency and recovery
Use a new idempotency key for a new release. Recover ambiguous success only by replaying the same key and identical request.
Response guidance
A released_to_production result identifies the new active mapping revision. Do not treat a review proposal as equivalent to release.
Success response
No synthetic example is approved for this operation. Use the success schema and response guidance above.