API reference
Enrich
Every match has a reason. Open the product
GET/v1/enrichOpen ↗
One transaction. A link, so an answer somebody disagrees with is a link they can paste into a bug report.
| Query | |
|---|---|
description | the bank description, exactly as the feed wrote it — store numbers, suburbs and card fragments and all, because resolving those is most of the work |
amount | the amount, signed: credits positive, debits negative. |
POST/v1/enrichKey
A list of transactions, up to 20,000 in one request, with the coverage of the whole list.
{"transactions": [{"id": "1", "date": "2026-08-02", "description": "WOOLWORTHS 1248 RICHMOND", "amount": -142.86}]}GET/v1/enrich/rulesOpen ↗
What the engine is made of: the categories it can assign and how many rules it holds.
GET/v1/enrich/accuracyOpen ↗
What it gets right, measured against payee lists nobody here chose, per category and per confidence band.