Transactions

Once a transaction has been enriched it is persisted for later retrieval through the API and for detection of regular transactions.

Through the API you can, for example, list transactions belonging to a user or account, search for transactions, or assign a category override to a transaction. The enhanced transactions API provides enhanced location and merchant data for a given transaction.

Request asynchronous enrichment

For asynchronous use-cases send batches of transactions to the Kafka transaction ingress topic.

Request synchronous enrichment

For synchronous use-cases a batch of transactions can be enriched using the Enrich transactions endpoint.

Update a transactions category

Updating a transaction category sets a userCategoryId override on the transaction. The category can be either a standard Moneyhub L2 category ID or one of the user's custom categories.

Use the required recategorisationType query parameter to control whether the override applies to this transaction only (single) or to this and future matching transactions for that user (future). The model-produced L1 and L2 values remain on the transaction alongside the override. See Categories for full details.

Split a transaction

Transactions can be split into parts and those parts given different descriptions, categories and amount. The total amount of the splits must equal the transaction amount.

Splits can be deleted, restoring the transaction to its original state, and all splits can be replaced at once with a call to the Upsert transaction splits endpoint.