Update Transactions for a Business
Scopes: transaction:update
Authorizations
The access token received from the authorization server in the OAuth 2.0 flow.
Path Parameters
The id of the business
"biz_GA6EG2qFxA97NZHtxeLPUy"
Body
The ID of the Transaction to update
"txn_WQMDNUHpBThYSNh4AprDBo"
The updated type of the Transaction
business, personal "business"
Whether the Transaction has been reviewed
Inline tag input to merge into the transaction's tags. Each key is a tag field name that must already exist. A list of {value, amount} objects replaces all current values for that field; a bare string is still accepted as a backwards-compatible alias for a single-value list. A null (or empty list) removes all of the transaction's values for that field. Fields not mentioned are left untouched. Per-field amounts follow the default rules (single value -> transaction amount; N values without amounts -> transaction.amount / N; mixed is rejected) and the per-field sum must not exceed transaction.amount.
{ "Location": "NYC" }Response
Successful Response
255"1234567890"
520.56
The description of the Transaction
512"Payment from Acme Corp"
The type of the Transaction
business, personal "business"
"personal"
The ID of the Transaction
"txn_WQMDNUHpBThYSNh4AprDBo"
The ID of the External Account associated with the Transaction
"eac_WQMDNUHpBThYSNh4AprDBo"
The invoice payments associated with the Transaction
null
The refund payments associated with the Transaction
null
The bill payments associated with the Transaction
null
Tag field name to the list of values attached to the transaction. Each value carries its allocated amount and, when pinned, its ledger; a single-value field is still returned as a one-element list.
{
"Job": [
{
"amount": "3000.00",
"value": "Maple Street Remodel"
},
{
"amount": "1500.00",
"value": "Downtown Office Rewire"
}
]
}