topic Re: Finding IPs Used by Meraki to Allow Webhook Requests on Firewall in Network Platform API

Finding IPs Used by Meraki to Allow Webhook Requests on Firewall

Eddysanoli — Thu, 13 Mar 2025 20:31:58 GMT

Hello, I have setup webhooks in a custom application to allow for active monitoring. Once deployed in production, the step that's failing is the communication between the webhook and our backend server. The reason is that the server is behind a firewall. We would like to know what are the possible hosts/IPs used by meraki, so that we can whitelist them.

Do they change per network? Is there a way to fetch them automatically?

I do see this in the documentation, but I dont fully understand it. If someone could help me clarify where I can find this info, I would be very grateful

Thank you

Re: Finding IPs Used by Meraki to Allow Webhook Requests on Firewall

mloraditch — Thu, 13 Mar 2025 20:40:52 GMT

You would for example need to allow those listed subnets access to your backend server on TCP/443. They can change per org and you can pull up your org under the question mark on the upper right and then firewall info.

Re: Finding IPs Used by Meraki to Allow Webhook Requests on Firewall

RWelch-USA — Thu, 13 Mar 2025 20:41:16 GMT

I think because it's coming from the Dashboard the answer to your Q is at the very bottom of that document although not host or IPs rather subnets.

Source IP range:
209.206.48.0/20
216.157.128.0/20
158.115.128.0/19

Re: Finding IPs Used by Meraki to Allow Webhook Requests on Firewall

michalc1 — Fri, 14 Mar 2025 02:16:59 GMT

Hi @Eddysanoli,

I'd recommend reviewing the Upstream Firewall Rules for Cloud Connectivity and applying them on the firewall.

A complete list of destination IP addresses, ports, and their respective purposes can be found in dashboard under "Help > Firewall info".

Re: Finding IPs Used by Meraki to Allow Webhook Requests on Firewall

Eddysanoli — Fri, 14 Mar 2025 16:35:25 GMT

Yes! Thank you very much. I was a bit confused on where to find the firewall info. Thought it was a network specific setting so I was lost. But after adding the required subnets onto our firewall, its now working as expected