Validate a posting against live state without committing
Walks the entire posting path against live state - vocabulary, account locks, floors, owner floors, preconditions, limit claims, closed periods - and then rolls everything back.
/v1/ledgers/{ledgerId}/postings/dry-runWalks the entire posting path against live state - vocabulary, account locks, floors, owner floors, preconditions, limit claims, closed periods - and then rolls everything back. 204 means the identical posting would have succeeded at this moment; any refusal is the same problem the real posting would have returned. Nothing is written, no claim is consumed and no idempotency key is spent, so the answer is advice about now, not a reservation for later: use a pending when the answer has to keep holding.
Authorization
bearerAuth In: header
Path Parameters
uuidRequest Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Response Body
application/problem+json
curl -X POST "https://example.com/v1/ledgers/497f6eca-6276-4993-bfeb-53cbbbba6f08/postings/dry-run" \ -H "Content-Type: application/json" \ -d '{ "type": "string", "legs": [ { "account_id": "449e7a5c-69d3-4b8a-aaaf-5c9b713ebc65", "direction": "credit", "amount": 1, "commodity": "string" }, { "account_id": "449e7a5c-69d3-4b8a-aaaf-5c9b713ebc65", "direction": "credit", "amount": 1, "commodity": "string" } ] }'Post many transactions atomically, in order
Posts many transactions as one atomic unit, in request order: every transaction commits or none does, under a single Idempotency-Key whose stored result covers the whole batch.
Reserve funds (the pending phase of a two-phase posting)
The reserve half of a two-phase posting.