Confirm a Transaction's Reservations
Use this endpoint to confirm every reservation a transaction holds in a single call, addressing them by the ledger transactionId — phase two of the two-phase reservation flow. The response reports how many reservations were transitioned in flipped. A flipped value of 0 is a valid, idempotent success — the transaction held no open reservations.
Authorizations
API Key authentication. Used by single-tenant deployments (MULTI_TENANT_ENABLED=false). Sent on every /v1/* request.
Headers
The type of media of the resource. Must be application/json.
The API Key for authentication. This header is required for all endpoints except health checks.
A unique identifier used to trace and track each request.
Path Parameters
The ledger transaction correlation ID whose reservations you want to confirm or release.
Response
Indicates that the transaction's reservations were confirmed.
Body returned by the by-transaction confirm and release endpoints.
The ledger transaction whose reservations were transitioned.
The terminal state the reservations resolved to.
CONFIRMED, RELEASED How many reservations were transitioned. A value of 0 is a valid, idempotent no-op — the transaction held no open reservations.

