Incremental trigger operations at card scope
Perform incremental operations on merchant action triggers at the card scope.
See the account-scope PATCH endpoint for full documentation on supported operations (add, remove).
Documentation Index
Fetch the complete documentation index at: https://docs.spade.com/llms.txt
Use this file to discover all available pages before exploring further.
Authorizations
Path Parameters
Your unique identifier for the user
512Your unique identifier for the card
512Body
Request body for incremental merchant action trigger operations.
- For
add:merchantTriggersis required.triggerIdsis optional and ignored if provided. - For
remove:triggerIdsis required and must be a non-empty list.
The operation to perform:
add: Register new merchants or update existing ones via merchant matchingremove: Remove merchants (excluded from enrichment lookups)
add, remove List of merchant triggers to add. Required for the add operation.
If a trigger ID already exists, the old registration is replaced (upsert behavior).
Field requirements:
id,merchantName, andactionare always required- If location fields (address, city) are NOT provided,
websiteis required
1 - 100000 elementsList of trigger IDs to remove. Required and must be non-empty for the remove operation.
Trigger IDs that are not currently active are silently ignored (idempotent).
For add operations, this field is optional and ignored if provided — you may pass null, [], or omit it entirely.
512["merchant_123", "merchant_456"]
