Skip to main content

​
Authentication

Spade’s APIs use secret API key authentication, because it is the fastest approach available for low latency applications. Each of Spade’s API environments requires a unique key which is passed in the  X-Api-Key header: 
curl --request POST \
   --url https://east.sandbox.spade.com/transactions/cards/enrich \
   --header 'content-type: application/json' \
   --header 'X-Api-Key: SPADE-API-KEY' \
   --data '{ request }'

​
Environments

Spade provides servers located on both the East and West Coast as well as both a Production and Sandbox environment for each geo-located server.

Sandbox & Production

Your development environments should use our sandbox endpoints and your production environment should hit our production endpoints.
Sandbox and Production environments do not share the same API keys, recurrence, and custom user generated categories and category personalization.

East & West

We have servers located on both the East and West Coasts and recommend calling the server closest to your server location to minimize latency.

For best practices on reducing latency see our guide on reducing latency.
Counterparty and Location information is common across all environments. You can expect the same metadata to be returned for the same enrichment payload, regardless of environment.

​
Supporting multiple data sources and clients

Note: This feature is not enabled by defaut. To access this feature please contact sales@spade.com
For clients that have multiple data sources or support other clients as an embedded service provider or reseller we support segmenting requests through use of a billingProfile and organizationId . The billingProfile flag supports values of:
  • standard - typically used for segmenting different data sources
  • resell - used for segmenting different clients
In addition to the billingProfile you’ll want to specify an organizationId that aligns to the data source or client associated with the request you’re sending to us. Below is an example of how this information is provided in a card enrichment request:
Reseller example
{
  "billingProfile": "resell",
  "organizationId": "ClientABC",
  "userId": "12345",
  "cardId": "card_5678",
  "transactionId": "txn-1234",
  "merchantName": "JOE'S PIZZA",
  "amount": 18.35,
  "currencyCode": "USD",
  "categoryCode": "4814",
  "categoryType": "MCC",
  "city": "New York",
  "state": "NY",
  "country": "USA",
  "occurredAt": "2025-08-15T18:27:51.000Z"
}

​
Enrich your first transaction

  • Using Postman
  • Using cURL

​
Configuration

You can create a fork of Spade’s Postman collection by clicking this linkFirst you’ll want to ensure you update the collection with your correct API Key and environment URL by entering them in the corresponding current value fields and clicking ‘Save.‘Postman Image 1 Pn

​
Make the Postman request

The postman collection includes this test transaction we’ve provided, so all you need to do is click Send!Postman Image 2 Pn
Congratulations on enriching your first transaction! We recommend checking out our Enrichment guides to get started sending your own data.