23:56:18:801[ERROR] Your server rejected

status-update

webhook. Error: Request failed with status code 400 23:56:21:139[ERROR] Your server rejected

end-of-call-report

webhook. Error: Request failed with status code 400

Hi there! 👋 I see you're experiencing a session timeout during an API call, along with webhook rejection errors. I'm unable to determine the exact cause of your specific session timeout without more details about your setup. However, I can help explain potential causes for these issues and provide some troubleshooting steps. ## Potential Causes for Session Timeout Session timeouts during API calls can happen for several reasons: 1. **Network Connectivity Issues**: Problems with network connectivity can cause timeouts when joining a call using VAPI. 2. **Incorrect API Setup**: According to the information I found, incorrect VAPI setup can lead to timeouts. This could include using the wrong API keys or endpoints. 3. **Timeout Settings**: The default timeout is 7.5 seconds, and exceeding this limit can cause session timeouts. 4. **Server-Side Errors**: Server-side errors can prevent your server from sending back a response, leading to timeouts. ## Understanding the 400 Error for Webhooks The 400 status code errors you're seeing with the

status-update

and

end-of-call-report

webhooks typically indicate a bad request. Here are some common reasons: 1. **Incorrect Request Format**: Your server might be rejecting the webhooks due to malformed JSON or missing required fields. According to the information I found, small deviations in key names or data structure can cause parsing issues. 2. **Webhook Configuration Issues**: Ensure that your webhook URL is correctly configured in VAPI and accessible from the internet. 3. **Mismatched Data**: The

toolCallId

in your response must match the

toolCallId

that was sent by VAPI in the initial request. ## Troubleshooting Steps Here are some steps you can take to troubleshoot these issues: 1. **Check Server Logs**: Look into your server logs to see if there are any specific errors that might be preventing the webhook from being processed correctly.

Hey, these are normal error logs. Your have selected these two server messages, but your server URL has rejected them. The same response was logged for your call. They are either safe to ignore or not; it depends on you.

@Shubham Bajaj , I understand but when i ask my assistant to make an api api it the call get cut off and then when i check the log its session time out error, and that was when i was making a call with twillo phone number to my assistant

Hey! To help track down this issue, could you share: - The call ID - What response you expected to get - What response you actually got instead This would really help us figure out what went wrong!

Message marked as helpful by @Deepak Kumar! 🎉

Hello @User I am using n8n hosted on Hostinger server, and when I test the tools from tools tab in vapi its correct triggering and getting reposnse successfully, But during Call the funtions are not trigger even a single time, and when I am checking in Call logs it showing me these errors, and I checked everything fine in server side, and all the settings are pefect in vapi as it was working yesterday, its stopped in live caimpaingn https://cdn.discordapp.com/attachments/1358230410269691985/1388117263323893880/image.png?ex=685fd071&is=685e7ef1&hm=52a747aec8f2c609893e0fa9e2967ab55c9be8b63456647745f476756cfe3ff8&

Can you send me the call_id?