Get EnterpriseOpen Dashboard

Transactions

Update inflight

Commit or void an inflight transaction.

PUT/transactions/inflight/{transaction_id}

Authorization

If set, the API uses an API key for authentication. Include the following header in your requests: X-blnk-key: <api-key>.

Replace <api-key> with your secret API key. Ensure the key is kept secure and not exposed in public repositories or client-side code.

See also: Core API key.

Path

transaction_idstringrequiredpath

The unique id of the inflight transaction.

Body

statusstringrequiredbody

Specifies the instruction for the inflight.

  • commit means the conditions were met and transaction should be processed.
  • void means the conditions were not met and amount should be rolled back.
precise_amountintegerbody

The commit amount in its smallest unit for a partial commit (recommended). Learn more: Commit part of a transaction.

amountfloatbody

Amount to commit for a partial commit. Blnk converts it using the inflight transaction’s precision. When both are set, precise_amount takes precedence over amount.

skip_queuebooleandefault falsebody

When false (default), the commit or void is enqueued for asynchronous processing and the response includes queued: true. When true, Blnk processes the action synchronously and returns an immediate APPLIED or VOID child. See Commit inflight and Void inflight.

dry_runbooleandefault falsebody

When true, Blnk projects the commit or void without settling anything. The hold stays in place. See Dry-run a transaction.

Response

When skip_queue is false, the body is the still-inflight transaction plus queued: true. When skip_queue is true, the body is the applied or voided child and queued is absent. A dry run uses the dry-run shape.

queuedboolean

true when the commit or void was accepted onto the queue and has not been applied. The transaction stays INFLIGHT until a worker finishes it.

The other fields match Record a transaction.