We have multiple developers on the team that are working on our mobile IAP implementation, which means they all have to receive webhooks on their local dev machines to test things. So far we have been managing this by just changing the webhook URL as different people test, as well as having multiple RC apps to test with. This can be pretty cumbersome because we can’t duplicate apps, we have to create new ones fresh and go through the process of copying the existing configuration from the old app.
It would be so much easier if we could just configure multiple endpoints that all webhooks get sent to. Is this possible, or something that we could get added to your backlog?
Best answer by tinaView original
Multiple webhook support is something we’ve heard before. It is currently in the backlog for evaluation and will be discussed within the team sometime in the future. However, I can’t promise if or when the team will build this exact feature. As a workaround for now, you can route webhook events to a server, then forward these payloads to multiple local dev machines.
I’d like to share how we have solved this issue: we are using Nginx to route our traffic. They have a module that does the forwarding for you: http://nginx.org/en/docs/http/ngx_http_mirror_module.html. It’s also available for the Nginx Ingress Controller with annotations; https://github.com/kubernetes/ingress-nginx/blob/main/docs/user-guide/nginx-configuration/annotations.md#mirror.
This does not take away the fact that RevenueCat should view the event-webhook relation as 1-to-many instead of 1-to-1.
I’d like to upvote for this feature. Forwarding the payloads is a bit more work than I’d like to have my team work on right now.