--- title: "Create Ledger Transaction Partial Post" method: POST path: "/ledger_transactions/{id}/partial_post" --- # Create Ledger Transaction Partial Post `POST /ledger_transactions/{id}/partial_post` ## Path parameters - `id` string, required ## Request body - object - `posted_ledger_entries` object[], required — An array of ledger entry objects to be set on the posted ledger transaction. There must be one entry for each of the existing entries with a lesser amount than the existing entry. - `amount` integer, required — Value in specified currency's smallest unit. e.g. $10 would be represented as 1000. Can be any integer up to 36 digits. - `direction` string, required — One of `credit` or `debit`. - `ledger_account_id` string, required — The ledger account that this ledger entry is associated with. - `lock_version` integer — Lock version of the ledger account. This can be passed when creating a ledger transaction to only succeed if no ledger transactions have posted since the given version. See [this guide](https://docs.moderntreasury.com/docs/handling-concurrency#using-the-lock_version-field) for more details. This will trigger synchronous processing, which imposes an additional rate limit on the API. See [Synchronous Ledger Entry Rate Limiting](https://docs.moderntreasury.com/docs/synchronous-ledger-entry-rate-limiting) for details. - `pending_balance_amount` object — Use "gt" (>), "gte" (>=), "'lt" (<), "lte" (<=), or "eq" (=) to lock on the account’s pending balance. If any of these conditions would be false after the transaction is created, the entire call will fail with error code 422. See [this guide](https://docs.moderntreasury.com/docs/handling-concurrency#locking-on-account-balance) for more details. This will trigger synchronous processing, which imposes an additional rate limit on the API. See [Synchronous Ledger Entry Rate Limiting](https://docs.moderntreasury.com/docs/synchronous-ledger-entry-rate-limiting) for details. - `lt` integer - `lte` integer - `eq` integer - `gte` integer - `gt` integer - `not_eq` integer - `posted_balance_amount` object — Use "gt" (>), "gte" (>=), "'lt" (<), "lte" (<=), or "eq" (=) to lock on the account’s posted balance. If any of these conditions would be false after the transaction is created, the entire call will fail with error code 422. See [this guide](https://docs.moderntreasury.com/docs/handling-concurrency#locking-on-account-balance) for more details. This will trigger synchronous processing, which imposes an additional rate limit on the API. See [Synchronous Ledger Entry Rate Limiting](https://docs.moderntreasury.com/docs/synchronous-ledger-entry-rate-limiting) for details. - `lt` integer - `lte` integer - `eq` integer - `gte` integer - `gt` integer - `not_eq` integer - `available_balance_amount` object — Use "gt" (>), "gte" (>=), "'lt" (<), "lte" (<=), or "eq" (=) to lock on the account’s available balance. If any of these conditions would be false after the transaction is created, the entire call will fail with error code 422. See [this guide](https://docs.moderntreasury.com/docs/handling-concurrency#locking-on-account-balance) for more details. This will trigger synchronous processing, which imposes an additional rate limit on the API. See [Synchronous Ledger Entry Rate Limiting](https://docs.moderntreasury.com/docs/synchronous-ledger-entry-rate-limiting) for details. - `lt` integer - `lte` integer - `eq` integer - `gte` integer - `gt` integer - `not_eq` integer - `show_resulting_ledger_account_balances` boolean — If true, response will include the balance of the associated ledger account for the entry and will trigger synchronous processing, which imposes an additional rate limit on the API. See [Synchronous Ledger Entry Rate Limiting](https://docs.moderntreasury.com/docs/synchronous-ledger-entry-rate-limiting) for details. - `metadata` string, json — Additional data represented as key-value pairs. Both the key and value must be strings. - `description` string — An optional free-form description for the posted ledger transaction. Maximum of 1000 characters allowed. - `effective_at` string, date — The timestamp (IS08601 format) at which the posted ledger transaction happened for reporting purposes. - `metadata` string, json — Metadata to be added to the posted ledger transaction. Must be a JSON object. ## Response `201` 201 - object - `id` string - `object` string - `live_mode` boolean - `external_id` string - `ledgerable_type` unknown - `ledgerable_id` unknown - `ledger_id` string - `description` unknown - `status` string - `reverses_ledger_transaction_id` string - `reversed_by_ledger_transaction_id` unknown - `partially_posts_ledger_transaction_id` string - `ledger_entries` object[] - `id` string - `object` string - `live_mode` boolean - `amount` integer - `direction` string - `status` string - `ledger_account_id` string - `ledger_account_currency` string - `ledger_account_currency_exponent` integer - `ledger_account_lock_version` integer - `ledger_transaction_id` string - `resulting_ledger_account_balances` object - `pending_balance` object - `credits` integer - `debits` integer - `amount` integer - `currency` string - `currency_exponent` integer - `posted_balance` object - `credits` integer - `debits` integer - `amount` integer - `currency` string - `currency_exponent` integer - `available_balance` object - `credits` integer - `debits` integer - `amount` integer - `currency` string - `currency_exponent` integer - `discarded_at` unknown - `created_at` string - `updated_at` string - `posted_at` string - `effective_at` string - `effective_date` string - `metadata` object - `created_at` string - `updated_at` string ## Other responses - `422` — 422 --- [API](https://skmtc.net/modern-treasury/apis/modern-treasury-api.md) · [All operations](https://skmtc.net/modern-treasury/apis/modern-treasury-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/modern-treasury/modern-treasury-api/versions/ed0431a2dcd0/schema)