+2Hi,
we have internal test servers where we would also like to develop our webhook endpoints on so we can test receiving events from the RevenueCat API. Those servers are obviously only accessible from our internal network by default.
To make the webhook URLs accessible for RevenueCat, I’d like to know what IP range the requests would be coming from, so I can configure our firewall accordingly.
Thanks a lot,
Markus
Best answer by Markus Wolff
Hey Markus!
Right now, the webhook IP range is variable so there isn’t anything fixed to hardcode on your side. To authenticate requests you can add an authorization token to the webhook configuration in RevenueCat that you can then verify on your server.
Thanks Ryan, we solved it by using a reverse proxy instead :-)
+9Hey Markus!
Right now, the webhook IP range is variable so there isn’t anything fixed to hardcode on your side. To authenticate requests you can add an authorization token to the webhook configuration in RevenueCat that you can then verify on your server.
+2Hey Markus!
Right now, the webhook IP range is variable so there isn’t anything fixed to hardcode on your side. To authenticate requests you can add an authorization token to the webhook configuration in RevenueCat that you can then verify on your server.
Thanks Ryan, we solved it by using a reverse proxy instead :-)
+2Hi
Does the IP range still variable or do you have some static IP? Here in company we’ve facing problems to use RevenueCat Webhook, because we are blocking every IP outside Brazil.
Thanks
Hi! I’d also like to know if you have configured static IPs? If not, it would be a great security feature to add. A lot of orgs have a default deny-all inbound firewall policy, and without static IPs from integrations it’s impossible to allow them in.
Thanks,
Michael
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
