Merchant search is in beta and is not enabled by default. To request access, contact us at sales@spade.com.
Overview
Merchant search lets you query Spade’s merchant database by name. It is designed for powering autocomplete experiences — as a user types, your application queriesGET /corporations and displays matching merchants with their name, logo, and website. The endpoint returns up to five results ordered by relevance.
Use the returned name and website to register merchants with Spade’s action triggers endpoint for rewards, merchant-locked cards, and other transaction-level actions.
Searching for a merchant
Send aGET request to /corporations with the merchant name as a query parameter.
Response
Response fields
| Field | Type | Description |
|---|---|---|
name | string | The merchant’s name |
logo | string | null | URL of the merchant’s logo, or null if unavailable |
website | string | null | The merchant’s website, or null if unavailable |
Building a merchant autocomplete
Backend proxy
Your backend should proxy requests to Spade so that your API key is never exposed to the client.Frontend debounce
Because the endpoint is rate-limited, debounce requests from the frontend so that a request is only sent after the user pauses typing (300-400 ms is a good starting point). Most autocomplete libraries handle this automatically — if yours does not, use a utility likelodash.debounce.
Next steps
- Merchant-based rewards — build a rewards program on top of merchant search
- Merchant-locked cards — restrict card spending to specific merchants
- Realtime action triggers — register rules that trigger custom actions during enrichment

