Webhooks - How would you use them with FreeAgent?

Hey :wave:t3:

I’m Stu, the Core Services:API Product Manager at FreeAgent. If you’ve posted on the forum recently then we’ve probably spoken, but if not then nice to meet you :grinning:

I’m very keen to hear from developers who would like to see FreeAgent support webhooks, and more specifically, context around how you might envision using them, why they would benefit you, for what areas of an account would you use them for etc.

We’re doing some exploratory research in this area so please feel free to post your thoughts and opinions here, and as always the more context the better. Consider this thread a single feature request that everyone is welcome to contribute to. :family_man_woman_girl_boy:


Stu McEwan
Core Services:API Product Manager

Webhooks would significantly reduce the read load I put on the API. Currently I read lots of data from many of the API’s collection endpoints every 30 minutes (reducing to every 10 minutes soon). If webhooks existed I would only need to bulk-read each resource once, and from then on I could just listen to the webhooks for changes.

While it’s always nice to do existing things more efficiently, I’m much more excited at the prospect of webhooks for deletions. The API doesn’t provide a way to find out what’s been deleted in FreeAgent (as has been noted here before :slight_smile: ) and there isn’t a neat way to derive it either. My system not knowing that a resource has been deleted in FreeAgent generates a steady stream of support requests for me from my users. Deletion webhooks would be a whole new capability rather than a variation on existing capabilities.

After deletion webhooks, the most useful one for me would be hearing when new bank transactions have been created. Most of the things my system does revolve around explaining bank transactions and it would be nice to be able to do that as soon as transactions appear in FreeAgent, rather than at the next scheduled sync.