Spade now offers the /transaction-rules endpoints for creating card-specific rules that get evaluated at enrichment time against enrichment outputs. For instance, you can set up rules to ensure a card is only used at a specific merchant, or to ensure a card is only used for certain spend categories, a combination of the two, and more. Transaction rules currently support counterparty_id, third_party_id, city, region, channel, amount, mcc, and category_code. Contact [email protected] for more information.

Spade now offers the merchants/ and /merchants/advanced/ endpoints for searching our database of merchants. Whether you're integrating with Spade's spending controls API, or looking to make transaction authorization decisions using Spade's data, you can find detailed merchant information through these new endpoints. Contact [email protected] to get started.

We now support parsing of certain DE43 formats via /transactions/enrich/parse. If the de43 can be parsed we use the parsed information instead. Because there is no standard de43 format, if you have pre-parsed data or are able to parse your own then we recommend using the /transactions/enrich/ endpoint.

On march 29th we published V2.02 which includes some slight changes to the formatting of the API. The changes were made in an attempt to make the API operate more consistently, improve usability and discoverability.

For each counterparty and location we match to in a transaction enrichment, we will now include a match_score which is a number from 0 to 100 indicating how strong of a match this is. This enables you to build products with confidence and make decisions on how to proceed for your particular use case.

Data quality and coverage are top priorities at Spade and we strive to continuously improve both. Feedback from our users can be invaluable for alerting us to errors or inconsistencies in our data or matching process.