Hey Vapi team — we’ve got a confirmed working webhook setup (AWS Lambda via API Gateway) with the correct URL and x-vapi-secret. The first end-of-call-report came through fine, but now none of the test calls are triggering any webhook despite correct config. We verified: Working endpoint (confirmed via curl) Fast 2xx responses end-of-call-report in serverMessages No logs in Lambda for failed calls Can someone take a look? We’re prepping a launch and need reliable post-call events. Happy to share full assistant config if needed. Thanks!

Since your webhook setup is confirmed and the issue persists, the most actionable next step is to share your full assistant configuration and recent call IDs with Vapi support for direct investigation. This approach is recommended in the documentation and community discussions for intermittent webhook delivery issues, as backend review may reveal platform-specific causes not visible from your end. If you recently changed SIP or webhook settings, mention those details as well for faster troubleshooting. Sources: - [Vapi Server URL documentation](https://docs.vapi.ai/server-url) - [Vapi Server Events documentation](https://docs.vapi.ai/server-url/events) - [Vapi Discord community: webhook delivery issues](https://discord.com/channels/1211482211119796234/1372358449761091584)

Make sure your assistant’s serverUrl and serverMessages include the correct settings, check that calls are ending properly with valid endedReason, confirm your API Gateway and Lambda are receiving requests, and if all configs look right..

Hey! To help track down this issue, could you share: - The call ID This would really help us figure out what went wrong!