Spade Category Action Triggers API

Register category action triggers and receive triggered actions in enrichment responses

Operations 16

Each operation below carries the questions people ask an LLM about it and the instructions they give an agent to run it. Generated by API Evangelist overlay

GET /category-action-triggers Check account-wide category trigger status · Get account-level category trigger status #
Ask an LLM
“Have my account-wide category action triggers finished registering yet?”
“Which version of the category triggers applies to every user in my account?”
Tell an agent
Show the status and version of my account-level category triggers.
Confirm the account-wide category trigger registration has succeeded.
PUT /category-action-triggers Replace account-wide category triggers · Register category triggers at account scope #
Ask an LLM
“How do I flag every transaction in a spending category across my whole account with Spade?”
“Can I set an action that fires on a category for all my users at once?”
Tell an agent
Register these category triggers {categoryTriggers} for my entire account.
Overwrite the account-wide category trigger list with {categoryTriggers}.
PATCH /category-action-triggers Add or remove individual account category triggers · Incremental category trigger operations at account scope #
Ask an LLM
“Can I add one category trigger to my account without resending the whole list?”
“Is there a way to delete just a few account-level category triggers by ID?”
Tell an agent
Add category triggers {categoryTriggers} to my account, keeping the existing ones ({operation}).
Run a {operation} on account category triggers with IDs {triggerIds}.
DELETE /category-action-triggers Clear all account-wide category triggers · Clear account-level category triggers #
Ask an LLM
“How do I wipe every category trigger set at the account level?”
“Does clearing account category triggers keep a version history?”
Tell an agent destructive · confirm first
Remove all category action triggers at my account scope.
Empty out the account-level category trigger list.
GET /programs/{programId}/category-action-triggers Check a program's category trigger status · Get program-level category trigger status #
Ask an LLM
“Are the category triggers for one of my card programs active yet?”
“What version of category triggers is registered for a specific program?”
Tell an agent
Show the category trigger status for program {programId}.
Check whether program {programId} category trigger registration succeeded.
PUT /programs/{programId}/category-action-triggers Replace a program's category triggers · Register category triggers at program scope #
Ask an LLM
“How do I attach category actions only to transactions tagged with one program?”
“Can different card programs have their own category trigger sets?”
Tell an agent
Register category triggers {categoryTriggers} for program {programId}.
Overwrite program {programId}'s category trigger list with {categoryTriggers}.
PATCH /programs/{programId}/category-action-triggers Add or remove a program's category triggers · Incremental category trigger operations at program scope #
Ask an LLM
“Can I add a single category trigger to a program incrementally?”
“How do I drop specific category trigger IDs from one program?”
Tell an agent
Add category triggers {categoryTriggers} to program {programId} using operation {operation}.
Apply {operation} to program {programId} category triggers {triggerIds}.
DELETE /programs/{programId}/category-action-triggers Clear a program's category triggers · Clear program-level category triggers #
Ask an LLM
“How do I remove every category trigger from a single program?”
“Can I reset one program's category actions without touching account-wide ones?”
Tell an agent destructive · confirm first
Clear all category triggers for program {programId}.
Empty the category trigger list on program {programId}.
GET /users/{userId}/category-action-triggers Check a user's category trigger status · Get user-level category trigger status #
Ask an LLM
“Are the category triggers for one particular user registered successfully?”
“What category trigger version applies to all cards of a given user?”
Tell an agent
Show the category trigger status for user {userId}.
Check if user {userId}'s category triggers are active.
PUT /users/{userId}/category-action-triggers Replace a user's category triggers · Register category triggers at user scope #
Ask an LLM
“How do I set category actions that apply to every card a single user holds?”
“Can each end user have their own category trigger list?”
Tell an agent
Register category triggers {categoryTriggers} for user {userId}.
Overwrite user {userId}'s category trigger list with {categoryTriggers}.
PATCH /users/{userId}/category-action-triggers Add or remove a user's category triggers · Incremental category trigger operations at user scope #
Ask an LLM
“Can I add one category trigger for a user without replacing their others?”
“How do I remove particular category trigger IDs for a single user?”
Tell an agent
Add category triggers {categoryTriggers} for user {userId} with operation {operation}.
Apply {operation} to user {userId}'s category triggers {triggerIds}.
DELETE /users/{userId}/category-action-triggers Clear a user's category triggers · Clear user-level category triggers #
Ask an LLM
“How do I wipe out all category triggers for one user?”
“Can I reset a single user's category actions to nothing?”
Tell an agent destructive · confirm first
Clear all category triggers for user {userId}.
Empty the category trigger list for user {userId}.
GET /users/{userId}/cards/{cardId}/category-action-triggers Check a card's category trigger status · Get card-level category trigger status #
Ask an LLM
“Are the category triggers on one specific card registered and active?”
“Which category trigger version applies to a single card only?”
Tell an agent
Show the category trigger status for card {cardId} of user {userId}.
Check whether card {cardId} belonging to {userId} has succeeded category triggers.
PUT /users/{userId}/cards/{cardId}/category-action-triggers Replace a card's category triggers · Register category triggers at card scope #
Ask an LLM
“How do I set category actions that fire only on one card, not the user's other cards?”
“Can a single card carry its own category trigger list?”
Tell an agent
Register category triggers {categoryTriggers} on card {cardId} for user {userId}.
Overwrite the category triggers on user {userId}'s card {cardId} with {categoryTriggers}.
PATCH /users/{userId}/cards/{cardId}/category-action-triggers Add or remove a card's category triggers · Incremental category trigger operations at card scope #
Ask an LLM
“Can I add a category trigger to just one card incrementally?”
“How do I drop specific category trigger IDs from a single card?”
Tell an agent
Add category triggers {categoryTriggers} to card {cardId} of user {userId} via {operation}.
Apply {operation} to card {cardId} (user {userId}) category triggers {triggerIds}.
DELETE /users/{userId}/cards/{cardId}/category-action-triggers Clear a card's category triggers · Clear card-level category triggers #
Ask an LLM
“How do I remove every category trigger from one card?”
“Can I clear a card's category actions while keeping the user-level ones?”
Tell an agent destructive · confirm first
Clear all category triggers on card {cardId} for user {userId}.
Empty the category trigger list for user {userId}'s card {cardId}.

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/spade:spade-category-action-triggers-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

spade-category-action-triggers-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Spade Category Action Triggers API
  description: Documentation for Spade's card transaction enrichment API and related endpoints. We offer sandbox and production environments on both the east coast and west coast to enable ultra low latency enrichment for realtime applications. Each environment requires different API keys. To inquire about API keys, please contact your Spade representative or reach out to .
  version: 2.7.3
servers:
- url: https://east.sandbox.spade.com
  description: East coast sandbox environment
- url: https://east.api.spade.com
  description: East coast production environment
- url: https://west.sandbox.spade.com
  description: West coast sandbox environment
- url: https://west.api.spade.com
  description: West coast production environment
- url: https://sandbox.v2.spadeapi.com
  description: East coast sandbox environment (deprecated)
- url: https://v2.spadeapi.com
  description: East coast production environment (deprecated)
- url: https://sandbox.west.v2.spadeapi.com
  description: West coast sandbox environment (deprecated)
- url: https://west.v2.spadeapi.com
  description: West coast production environment (deprecated)
security:
- ApiKeyAuth: []
tags:


# --- truncated at 32 KB (34 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/spade/refs/heads/main/openapi/spade-category-action-triggers-api-openapi.yml