Post one balanced transaction

Posts one balanced transaction: legs in integer minor units that sum to zero per commodity, or nothing is written at all. Requires an Idempotency-Key; a replay within the retention window returns the original response byte for byte and posts nothing further. The whole refusal vocabulary is checked inside this one database transaction, under the accounts' own locks: unbalanced and invalid for a request the books could never take, insufficient_funds when a leg would breach an account's floor, account_frozen / account_closed, precondition_failed when a supplied version_is or min_available_after no longer holds, limit_exceeded when a limit_claims entry would push its aggregate past max, period_closed when effective_at falls inside a closed period, and post_exceeds_pending when post_pending_id is set and the debits exceed what that pending reserved. Claims and preconditions are consumed and checked in the same transaction as the money, which is what makes a cross-request cap authoritative here rather than advisory in the caller.

Path Parameters

Header Parameters

Response Body