In today's release we've introduced a new matchScore field in the location portion of our enrichments. Similar to the matchScore already found under the counterparty portion of an enrichment, a location matchScore is an assessment of how confident we are that a specific location was involved in a transaction. We've also updated our scoring model for our counterparty scores as we work to continually provide the highest quality assessment of our enrichments.

In today's release, we're consolidating our merchant search offering into the /merchants endpoint. All existing functionality from /merchants/advanced is being migrated over to /merchants. The /merchants/advanced endpoint will remain available for a time before being deprecated.

In today's release, we're consolidating our merchant search offering into the /merchants endpoint. All existing functionality from /merchants/advanced is being migrated over to /merchants. The /merchants/advanced endpoint will remain available for a time before being deprecated.

Today we're releasing v2.3.0 (backwards compatible as always) which adds four new endpoints allowing you to report the following information

To improve usability of our enrichment service we now parrot back the transaction id from the request in our responses. This change should makes it clear which enrichment response corresponds to each unenriched transaction should they ever become disconnected.

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.