API ReferenceChangelog
Changelog
added

Address Lines 1 and 2

Going forward, enrichments will include two new fields: addressLine1 and addressLine2. This change will hopefully improve usability of our location data.

added

Recurring Transaction Flagging

As of today we are releasing support for intelligent recurrence flagging. This system can identify in real time when a transaction is on a periodic billing cycle, such as a phone bill, or online subscription. Unlike competitors solutions which rely on a model to guess if a transaction is recurring, we are able to reference a given user's previous transactions in real time to show with evidence that a transaction is recurring.

added

Batch enrichment

We're excited to announce support for asynchronous batch enrichment of up to 50k transaction per request. This makes enriching large sets of transactions far more convenient.

added

Introducing new and improved match scores

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.

deprecated

Advanced Merchant Search endpoint is renamed

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.

added

Merchant Search Alternates

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.

added

Transaction Feedback

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

added

Parroting Transaction IDs

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.

added

Introducing Transaction Rules

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.

Introducing Merchant Search and Advanced Merchant Search

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.