Incremental category trigger operations at card scope
Perform incremental operations on category action triggers at the card scope.
See the account-scope PATCH endpoint for full documentation on supported operations (add, remove).
Authorizations
Path Parameters
Your unique identifier for the user
512Your unique identifier for the card
512Body
Request body for incremental category action trigger operations.
- For
add:categoryTriggersis 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 category triggers or update existing onesremove: Remove category triggers (excluded from enrichment lookups)
add, remove "add"
List of category triggers to add. Required for the add operation.
If a trigger ID already exists, the old registration is replaced (upsert behavior).
Field requirements:
id,categoryId, andactionare always required
1 - 300 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["travel-reward-1", "block-gambling"]

