Skip to main content

Fetch the default categories for your integration

The first thing you’ll likely want to do is fetch the default categories for your integration. This list contains all of the categories that Spade provides, plus any custom categories that you’ve added at integration-level (which should be none at this point).
Sending the above request returns a list containing all of Spade’s 250+ categories:
Note that Spade’s categories are hierarchical, so Accounting and Bookkeeping, for instance, sits underneath the Banking and Finance category, which sits at the root level. For convenience, each serialized category includes a fullCategoryHierarchy object, which contains the full hierarchy of the category.

Creating a custom category

Spade’s default categories are designed to meet the majority of use cases. However, there are some use cases where you may want to create custom categories specific to your integration. Custom categories can sit at the root level, under Spade’s categories, or under other custom integration-level categories. Here’s how you can create a custom category that sits at the root level:
Sending the above request creates a new custom category and returns a copy of the serialized category:
Here’s how you can create a custom category that sits under this category:
Sending the above request creates the new custom category and returns a copy of the serialized category:

Re-fetching the default categories for your integration

Now, if you re-fetch the default categories for your integration, you’ll see the two custom categories you just created:
Sending the above request returns a list containing all of Spade’s 250+ categories plus the new custom categories:
Notice that custom category IDs are UUIDs, while Spade’s default categories use a hierarchical numerical ID system. This is by design: our system uses different ID formats for custom and default categories to make it easy for you to distinguish between the two.

Recategorizing past transactions

To recategorize specific past transactions onto a custom category, you’ll want to update those transaction records in your internal system. For instance:

Recategorizing all future transactions for a specific counterparty

One of the most powerful features Spade provides is the ability for you to recategorize future transactions before they take place. This feature takes advantage of Spade’s ability to consistently match transactions to stable counterparty IDs using ground truth data. Here’s how you can recategorize future transactions for a specific counterparty across your entire integration:
With this personalization in place, any future transactions that take place at KinderCare Learning Centers will be enriched with the custom category, which will appear in the personalization section of the enrichment as the counterparty’s industry:

Deleting custom categories

You can delete custom categories all at once or individually. To delete all custom integration-level categories, send a DELETE request to the categories endpoint:
To delete a specific custom integration-level category, send a DELETE request to the categories/:id endpoint with the category’s ID:

Deleting counterparty category personalizations

You can delete counterparty category personalizations all at once or individually. To delete all counterparty category personalizations, send a DELETE request to the /counterparty-category-personalizations endpoint:
To delete a specific counterparty category personalization, send a DELETE request to the /counterparty-category-personalizations/:counterpartyId endpoint with the counterpartyId of the personalization you want to delete:

FAQs

What if I want to recategorize transactions based on the industry instead of the counterparty?

We don’t currently support category-wide personalizations. However, you can achieve this on your end by creating Spade category -> custom category mappings on your end.

Conclusion

You’ve just learned how Spade’s category personalization endpoints can be used to create custom categories at the integration-level and recategorize transactions onto those categories.

Next Steps

User Category Personalization Guide