@Support Team i emailed support last night sent more they requested this info and got nothing back so im posting here i been trying to get this web hook to work for 3 days 1. Failed Call IDs & Timestamps Call ID Timestamp (UTC) Error 0ed2a606-b91d-494d-ac63-2b1dc37add16 2025-05-25T04:22:23.019Z 403 IP not whitelisted a975c7fe-0310-4505-9367-d3f7aaa28a63 2025-05-25T05:15:42.331Z 403 IP not whitelisted 3c69047a-a907-4793-a663-71788d8d0076 2025-05-25T06:03:17.892Z 404 POST not registered 2. Expected vs. Actual Response Expected: json { "status": "success", "message": "Webhook processed" } Actual: json { "message": "Request failed with status code 403", "data": "IP is not whitelisted!" } 3. Evidence & Config Screenshots: n8n Webhook Settings (showing POST method, path /webhook/vapi-agent-response) IP Whitelist (Vapi IPs 44.229.228.186, 44.238.177.138 confirmed) Workflow: n8n Cloud Link (if shared) 4. Steps Taken Upgraded to n8n paid plan (no change). Manually tested webhook via curl → Same 403 error. Triple-checked IP whitelists in n8n + firewall. Request: Confirm if Vapi’s IPs have changed. Verify if n8n Cloud has hidden whitelist restrictions.

Vapi's current IPs for webhook/SIP traffic are:

44.229.228.186/32
44.238.177.138/32

These are the only IPs you need to allowlist according to the latest Vapi documentation. If you have already done this and still receive 403 errors, it's possible that n8n Cloud has additional internal restrictions—**contact n8n support to confirm if further allowlisting is required on their end** or if there are hidden firewall rules affecting webhook delivery. Source: - [Vapi SIP Trunking Documentation](https://docs.vapi.ai/advanced/sip/sip-trunk)

Hello Matt, We do not have static outbound IP ranges. Would a X-Server-Secret header be suitable for you?