Update an enriched transaction

Requires the caas:transactions:write scope. Recategorise a single enriched transaction by setting a userCategoryId. Use the recategorisationType query parameter to control whether the change applies to this transaction only (single) or to this and all future matching transactions (future). 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
string
required
length between 8 and 36

The account ID as specified on the transaction

string
required
length between 8 and 36

The Transaction ID

Query Params
string
enum

Specifies whether the recategorisation applies to this transaction only or to this and all future matching transactions.

Allowed:
Body Params
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

Language
Credentials
Bearer
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json