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 update the level 2 category of 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 can be used to personalise categorisation for a user, and will be taken into account in future when categorising similar transactions for that user. The category can be either a standard category or one of the users custom categories.

When a standard category is used this will also have a small influence on the future preferences of the model as a whole.

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 the category and description of a split can be updated . In order to change the amount all splits must be replaced at once with a call to the POST endpoint .