Update an enriched transaction

patch

https://api.moneyhub.co.uk/caas/v1/accounts/{accountId}/transactions/{transactionId}

Requires the caas:transactions:write scope. Recategorise a single enriched transaction by setting a userCategoryId. Use the recategorisationType query parameter to control scope: single (this transaction only), future (this transaction and all future matching transactions), or past-and-future (this transaction, a future matching rule, and asynchronous recategorisation of matching historical transactions). The PATCH response returns immediately with the updated target transaction; when using past-and-future, historical recategorisation is processed asynchronously. A transaction with active splits, identified by its userCategoryId being set to the mixed category, cannot be recategorised: the request returns 409 Conflict. Clear the splits with DELETE /accounts/{accountId}/transactions/{transactionId}/splits before recategorising.

Path Params

accountId

string

required

length between 8 and 36

^[a-zA-Z0-9-]+$

The account ID as specified on the transaction

transactionId

string

required

length between 8 and 36

^[a-zA-Z0-9-]+$

The Transaction ID

Query Params

recategorisationType

string

enum

Controls recategorisation scope. single: this transaction only. future: this transaction and future matching transactions. past-and-future: this transaction, a future matching rule, and matching historical transactions. The PATCH response reflects only the target transaction; historical updates for past-and-future are processed asynchronously.

Allowed:

Body Params

userCategoryId

string

required

The category to assign to this transaction. Accepts a custom category UUID or a standard Moneyhub L2 category ID (e.g. "22"). The reserved system category "mixed" cannot be assigned: it is applied automatically once the transaction has splits, to signal the transaction is divided across multiple categories.

Responses

200Successful Transactions Response

400Unsuccessful Response - Bad request

401Unsuccessful Response - Not authorised - Missing authorisation header - Invalid access Token

403Unsuccessful Response - Forbidden - Invalid scopes

404Unsuccessful Response - Resource not found

409Unsuccessful Response - Conflict - the transaction has active splits and cannot be recategorised