Transactions

Correct a transaction's category, and learn a merchant rule from it when asked

The customer category picker. The ledger follows the decision before the category is written: the posted journal entry is void-and-replaced with the bank or card offset kept and only the counterpart moved, then the category is saved as a manual decision. The change applies to this transaction only; a company merchant rule is written or repointed only when learnMerchantRule is true (#3112). A refused request writes nothing.

post/companies/{companyId}/transactions/{transactionId}/learn

Request

  • Base URL: https://api.medianfi.com/api/v1
  • URL: https://api.medianfi.com/api/v1/companies/{companyId}/transactions/{transactionId}/learn
  • Auth: HTTP bearer

Request body

glAccountIdstring uuid required
learnMerchantRuleboolean

#3112: whether this change also writes or repoints the company merchant rule for this transaction's merchant, so later transactions from the merchant take the category. true: it does. Absent or false: the category applies to this transaction only and the company's merchant rules are left alone. Stripe revenue transactions (a Stripe charge, invoice or subscription payment, or a Stripe counterparty-history suggestion) are outside this choice: their exact company rule is always written, because that rule is what lets the revenue entry post. A non-boolean value is a 422.

Response

Category saved (also returned when the transaction or account does not exist in this company)

Changes

No recorded changes to this operation across all 1 revision of this API.