Banking

Exclude many unposted bank transactions

Excludes up to 500 person-chosen unposted rows (for example the 'may be in register' filter) in one commit with one audit entry per row. Each row stays restorable. Posted and reconciled rows are refused per row. With possibleDuplicate=true instead of transactionIds it excludes every waiting row whose possible-duplicate partner is already posted (optionally on one bankAccountId) and reports undecidedPairs, the pairs where neither side is posted yet. Excluding a row clears its partner's possible-duplicate pill. Requires bank_transactions:read_write and manage:banking.

post/bank-transactions/exclude-batch

Request

  • Base URL: https://ledgerhq.pro/api/v1
  • URL: https://ledgerhq.pro/api/v1/bank-transactions/exclude-batch
  • Auth: one of:
    • HTTP bearer and API key in header x-organization-id
    • HTTP bearer and API key in header x-organization-id

Request body

transactionIdsstring[]

Unposted bank transactions to exclude. Omit when possibleDuplicate is true.

possibleDuplicatetrue

Exclude the leftover side of each possible-duplicate pair whose other side is posted

bankAccountIdstring uuid

With possibleDuplicate, limit to this account's feed

reasonstring

Optional audit reason

Response

Per-row result; HTTP 200 does not imply every row was excluded.

requestedinteger required
excludedinteger required
alreadyExcludedinteger required
failedinteger required
possibleDuplicateboolean
undecidedPairsinteger

Possible-duplicate pairs where neither side is posted yet (possibleDuplicate mode only)

Changes

No recorded changes to this operation across all 5 revisions of this API.