Register category triggers at card scope
Register category action triggers at the card scope.
Card-level triggers apply only to transactions for the specified card.
Field requirements:
id,categoryId, andactionare required for each triggercategoryIdmust be a valid Spade category ID (useGET /categoriesto discover valid IDs)
Limit: A maximum of 300 categoryTriggers can be submitted per request. All registrations are processed synchronously.
Important: Triggers are only applied to enrichment responses when the status is succeeded.
To learn more about action triggers, please read the Category Action Triggers Guide.
Authorizations
Path Parameters
Your unique identifier for the user
512Your unique identifier for the card
512Body
Request body for registering category action triggers.
List of category triggers to register for action matching. Each trigger must have a unique id.
Field requirements:
id,categoryId, andactionare always required
Limit: A maximum of 300 triggers across all scopes. All registrations are processed synchronously.
1 - 300 elementsResponse
Registration created successfully
Response containing the status of a category action trigger registration.
The current status of the action trigger registration. Category trigger registrations are processed synchronously, so the status is always one of:
succeeded: Registration complete, triggers are now activefailed: Registration failed, check your request and retry
succeeded, failed "succeeded"
The version number of this registration. Increments with each PUT, PATCH, or DELETE request to this scope.
1
The list of active category triggers registered for this scope. Present on GET responses; omitted on PUT and PATCH responses.
The total number of active category triggers registered for this scope. Present on GET responses; omitted on PUT and PATCH responses.
10

