Verify prerequisites
Before you start, make sure you have:
- A Yapily application with valid credentials
- Transaction data to categorise (in the correct format)
- Register a Webhook for notification events when categorisation is done or failed
Register a webhook
Categorisation works asynchronously and therefore requires a registered webhook for your application.Please follow our Webhook Registration Guide to register a webhook endpoint.You must also subscribe to the
transactions.categorisation.failed event to be notified of failures.Submit transactions for categorisation
Send your transaction data to Yapily for categorisation. Each transaction should include:Note the
id: Unique identifier for the transactiondate: Transaction datedescription: Transaction description (used for categorisation)amount: Transaction amountcurrency: Currency code (e.g., GBP, EUR)type: Transaction type (DEBITorCREDIT)
categorisationId - you’ll need this to retrieve the results.Understanding the enrichment data
Each categorised transaction includes anenrichment object with:
- categorisation.category: The primary category assigned to the transaction
- categorisation.categories: An array of all applicable categories (ordered by relevance)
- merchant.name: The clean merchant name (if identified)
- merchant.businessName: The full business name (if identified)
Available categories
Yapily categorises transactions into the following categories:- GROCERIES
- SHOPPING
- ENTERTAINMENT
- BILLS
- TRANSPORT
- EATING_OUT
- INCOME
- SALARY
- CASH
- TRANSFERS
- GENERAL
- And more…
Data retention
Next steps
- Learn about Transaction Categorisation
- Explore the Categorisation List
- See the Categorisation Tutorial for categorising Yapily-sourced transactions