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.
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.
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.
Enrich your first transaction
Configuration
You can create a fork of Spade's Postman collection by clicking the button below:
First 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.'
Make the Postman request
The postman collection includes this test transaction we've provided, so all you need to do is click Send!
Congratulations on enriching your first transaction! We recommend checking out our Enrichment guides to get started sending your own data.