Skip to main content
2026-03-16
Enrichment
v1.1.6

New ‘options’ field for enrichment endpoint

Added

  • Enrichment options on POST /v1/transactions/enrich: new optional options field in the request body.
    • Filters (options.filters): set noMerchant, noIntermediary, or noLocation to true to skip extraction of that entity type. Useful when you already have the data or want faster responses.
    • Pre-filled merchant (options.merchant): supply id, name, or domain when you know the merchant. The API will use it directly instead of extracting from the title. IDs must exist in our system (returns 422 if not found); names and domains use best-effort lookup.
    • Pre-filled location (options.location): supply cityName, streetName, storeNumber, physicalLocation, or coordinates to improve location accuracy.
    • Pre-filled intermediaries (options.intermediaries): supply up to 5 intermediaries by id, name, or domain when you know the payment processor(s).
    • You cannot combine a filter (e.g. noMerchant) with pre-filled data for the same entity type; the request will return 422.

Changed

  • Improved extraction accuracy for transaction titles that include country codes (e.g. NETFLIX NL).
  • Improved handling of reference-like patterns (payment IDs, order numbers)
  • When you pre-fill merchant and skip intermediary + location, the API may bypass title dissection for lower latency.

Fixed

  • Titles ending in a country code (e.g. NETFLIX NL) are now parsed correctly instead of being treated as merchant-only.
2026-03-12
Enrichment
v1.1.5

Incremental accuracy & performance improvements

This patch release focuses on enrichment accuracy and performance across the board:
  • Improved entity detection — better parsing of merchant names from noisy transaction strings, reducing false negatives in the entity detection stage
  • Enhanced timing — the enrichment endpoint now has faster cold-start performance
  • More reliable confidence scores — tuned reason-tag generation so confidence values more accurately reflect match quality, especially for location and merchant entities
  • Faster enrichment pipeline — incremental performance improvements to the /enrich pipeline for faster response times