Receiving multiple webhooks
# support
e
> We are receiving multiple webhooks for the same call, even though we have only enabled a single webhook on the server side — specifically the "End of Call Report" webhook. However, we are also receiving additional status update webhooks, which we have not configured. > > This is impacting our post-call flow and causing inconsistencies. Please suggest. Use case - Want to track answered and unanswered calls separately. https://cdn.discordapp.com/attachments/1359149337925386360/1359149338223444018/Screenshot_2025-04-08_at_6.22.20_PM.png?ex=67f66df6&is=67f51c76&hm=a3d3a6763d9a1628e8445fca03cbb4648d066a84b0b0c8e104386082ec57fe1f&
v
Hi there! 👋 I understand you're having issues with receiving multiple webhooks for the same call, even though you've only enabled the "End of Call Report" webhook. I can't see your specific configuration details to diagnose exactly why this is happening in your case, but I can definitely help with some potential causes and solutions for the unwanted webhooks, as well as how to track answered and unanswered calls separately. ## Why You Might Be Receiving Multiple Webhooks There are several possible reasons for receiving multiple webhooks: 1. **URL Precedence**: According to the [Vapi documentation](https://docs.vapi.ai/api-reference/assistants/update), webhook URLs follow a specific order of precedence: - assistant.server.url - phoneNumber.serverUrl - org.serverUrl You might have URLs configured at multiple levels. 2. **Application-Level vs. Account-Level Settings**: You might have settings at both the application and account levels with different configurations. 3. **Multiple Applications**: If you have multiple applications within your Vapi account, each might have its own webhook settings. 4. **Concurrency Issues**: Vapi might be experiencing concurrency errors that lead to duplicate webhook triggers. ## How to Resolve Unwanted Status Update Webhooks To prevent receiving unwanted status update webhooks: 1. **Check Webhook Configuration**: Review your webhook configuration in the Vapi Dashboard to ensure only the desired webhooks are enabled. 2. **Remove Unwanted Server Messages**: You can remove specific server messages through the Vapi Dashboard: - Go to the Vapi Dashboard - Click on Assistants in the NavBar - Select your Assistant - Go to the Advanced Tab - Scroll down to the server messages section and deselect any unwanted server messages 3. **Review Event-Specific URLs**: Check if you have different URLs set for different events and ensure they're configured correctly.
## Tracking Answered and Unanswered Calls Separately For tracking answered and unanswered calls separately using webhooks: 1. **Use the
endedReason
Field**: The End of Call Report webhook includes an
endedReason
field that can help differentiate between call outcomes. You can set up logic to detect different scenarios (answered, not answered, etc.) and use this field accordingly. 2. **Status-Update Server Event**: While you've disabled this, the "status-update" server event can provide information about call termination, including the reason, which can help identify unanswered calls. 3. **Voicemail Handling**: Be aware that Twilio treats voicemail pick-ups as answered calls, so you might need advanced detection or a fallback mechanism if this affects your tracking. Is there anything specific about these suggestions you'd like me to elaborate on further? Sources: - [Vapi documentation](https://docs.vapi.ai/api-reference/assistants/update) - [Vapi Server URL documentation](https://docs.vapi.ai/server-url) - [Vapi Server Events documentation](https://docs.vapi.ai/server-url/events)
r
Ok
s
Hey! To help track down this issue, could you share: - The call ID This would really help us figure out what went wrong!