The enrichment of transactions sourced by a Moneyhub connection

By default, all transactions retrieved through a Moneyhub-powered connection will be enriched with category and counterparty information. You can view the enriched transaction schema by examining the GET transaction endpoint. Transaction responses include categoryId and counterpartyId by default. For clients that request the transactions_details:read scope, responses also include l1CategoryName and l2CategoryName as kebab-case category keys, plus a nested counterparty object with display names and optional merchant details — reducing the need for separate lookups against the categories and counterparties endpoints. If you do not wish for this feature to be enabled for your client, then you can receive unenriched transactions. This alternative schema is presented here.

Enriching transactions sourced externally to a Moneyhub connection

When categorising transactions from an external source outside of Moneyhub, we offer two different approaches depending on your use case.

If you want to use Moneyhub to store transaction data for your users, then we recommend this approach to categorisation here

If your use case does not require creating account connections through Moneyhub for users or storing their transactions, we recommend using our Categorisation as a Service endpoint. For more information, see our documentation here