How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Spade Merchant Action Triggers API

Register merchant action triggers and receive triggered actions in enrichment responses

Spade Merchant Action Triggers API is one of 8 APIs that Spade publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Merchant Action Triggers. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 16 operations across 4 paths, and defines 5 schemas. It is described by OpenAPI 3.2.0, at version 2.7.3.

Requests are made against 8 base URLs: https://east.sandbox.spade.com, https://east.api.spade.com, https://west.sandbox.spade.com, https://west.api.spade.com, https://sandbox.v2.spadeapi.com, https://v2.spadeapi.com, https://sandbox.west.v2.spadeapi.com, https://west.v2.spadeapi.com.

16 operations 4 paths 5 schemas 4 DELETE4 GET4 PATCH4 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.7.3
Base URL
https://east.api.spade.com
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Spade Merchant Action Triggers API declares 1 security scheme for authenticating requests. An API key is passed in the header as X-Api-Key (ApiKeyAuth). By default, every request must be authenticated.

Paths & Operations 16

Across 4 paths, the API surfaces 16 operations — 4 DELETE, 4 GET, 4 PATCH, 4 PUT. Each is listed below with its method, path, parameters, and response codes.

Merchant Action Triggers 16

Register merchant action triggers and receive triggered actions in enrichment responses

DELETE
/merchant-action-triggers
Clear account-level triggers
merchantActionTriggersDelete → 204403500
GET
/merchant-action-triggers
Get account-level trigger status
merchantActionTriggersGet → 200403404500
PATCH
/merchant-action-triggers
Incremental trigger operations at account scope
merchantActionTriggersPatch body → 200201400403409500
PUT
/merchant-action-triggers
Register merchant triggers at account scope
merchantActionTriggersPut body → 201400403409500
DELETE
/users/{userId}/cards/{cardId}/merchant-action-triggers
Clear card-level triggers
cardMerchantActionTriggersDelete 2 params → 204403500
GET
/users/{userId}/cards/{cardId}/merchant-action-triggers
Get card-level trigger status
cardMerchantActionTriggersGet 2 params → 200403404500
PATCH
/users/{userId}/cards/{cardId}/merchant-action-triggers
Incremental trigger operations at card scope
cardMerchantActionTriggersPatch 2 params body → 200201400403409500
PUT
/users/{userId}/cards/{cardId}/merchant-action-triggers
Register merchant triggers at card scope
cardMerchantActionTriggersPut 2 params body → 201400403409500
DELETE
/programs/{programId}/merchant-action-triggers
Clear program-level triggers
programMerchantActionTriggersDelete 1 param → 204403500
GET
/programs/{programId}/merchant-action-triggers
Get program-level trigger status
programMerchantActionTriggersGet 1 param → 200403404500
PATCH
/programs/{programId}/merchant-action-triggers
Incremental trigger operations at program scope
programMerchantActionTriggersPatch 1 param body → 200201400403409500
PUT
/programs/{programId}/merchant-action-triggers
Register merchant triggers at program scope
programMerchantActionTriggersPut 1 param body → 201400403409500
DELETE
/users/{userId}/merchant-action-triggers
Clear user-level triggers
userMerchantActionTriggersDelete 1 param → 204403500
GET
/users/{userId}/merchant-action-triggers
Get user-level trigger status
userMerchantActionTriggersGet 1 param → 200403404500
PATCH
/users/{userId}/merchant-action-triggers
Incremental trigger operations at user scope
userMerchantActionTriggersPatch 1 param body → 200201400403409500
PUT
/users/{userId}/merchant-action-triggers
Register merchant triggers at user scope
userMerchantActionTriggersPut 1 param body → 201400403409500

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are MerchantTriggerItem (13 properties), ActionTriggerStatusResponse (4 properties), MerchantActionTriggerPatchRequest (3 properties), ActionTriggerPatchResponse (2 properties). Each schema is shown below with its type and property counts.

MerchantActionTriggerPatchRequest
object
Request body for incremental merchant action trigger operations. - For add: merchantTriggers is required. triggerIds is optional and ignored if provided. - For…
3 properties 1 required
ActionTriggerStatusResponse
object
Response containing the status of an action trigger registration.
4 properties
MerchantTriggerItem
object
A merchant trigger to register for action matching.
13 properties 3 required
MerchantActionTriggerRegistrationRequest
object
Request body for registering merchant action triggers.
1 property 1 required
ActionTriggerPatchResponse
object
Response for the remove PATCH operation.
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

spade-merchant-action-triggers-api-openapi.yml Raw ↑

Other APIs Spade publishes across the network.

Spade Card Enrichment API
Spade Category Action Triggers API
Spade Category Personalization API
Spade Feedback and Reporting API
Spade Merchant Search API
Spade Transfer Enrichment API
Spade Universal Enrichment API
Where this information came from

This is an independent, third-party profile of Spade Merchant Action Triggers API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.