Reactions to Improving Webhooks for Managing Events

API Feedback
1

Hi everyone,

I am working on integrating Patreon’s API into our application and wanted to gather some feedback on improving the webhook functionality for event handling; We are looking at how webhooks can be used more effectively for real time updates on various events, such as new pledges, changes in membership tiers & content updates.

Are there any best practices or recent changes in webhook handling that you would recommend? We have facing some challenges with handling event payloads efficiently & making sure that our system reacts promptly to these updates.

It will appreciated if you could offer any advice on handling high frequency events, guaranteeing data consistency or handling webhook retries.

Also when I was searching about this I came across these resources Using Patreon Webhooks to Initiate GitHub Actions Workflow & MuleSoft API witch help me a lot still need advice, if anyone have any resources, tutorials or personal experiences It would be greatly appreciated!!

Thank you… :smile:

2

The webhooks should ideally be processed asynchronously. Which framework do you use? I use PHP with Symfony, for example, and there is a queue system (Message Handler). When a webhook is sent to my system, I place a message with the required data in the queue and then give a direct response. There is then an asynchronous background process that processes the messages from the queue and then executes the logic.

1 Like
3

Ideally you would use webhooks, but also supplement it with a cron that regularly syncs your campaign members to your app so that you can check for their entitlements. That is, unless your users log into your application. If that is the case, you could have the users log in via Patreon and use their tokens to get their details. Or you can mix all of those, depending on your use case.