[400] Bad Request
# support
v
Hi there! I see you're encountering a [400] Bad Request error with Vapi. Unfortunately, I can't determine the exact cause of your specific error without more details about your implementation or the complete error message. However, I can definitely help with common causes and troubleshooting steps for 400 Bad Request errors in Vapi. ## Common Causes of 400 Bad Request Errors in Vapi Based on the information I found, here are some potential causes: 1. **Concurrency Limit Issues**: You might be exceeding the maximum number of concurrent calls allowed by your Voice API plan. 2. **Incorrect Credentials**: The error could occur if the
credentials
property is included in the API request when it shouldn't be. 3. **Input Validation Failure**: The input provided might not match the expected format or schema. 4. **Incorrect JSON Formatting**: Issues with the format of the JSON response, such as unescaped line breaks. 5. **Server-Side Errors or Timing Issues**: If there's an error on the server processing the request or if your server takes too long to respond. 6. **WebSocket Connection Issues**: Problems with invalid URLs, service outages, or authentication issues. 7. **SIP Connection Problems**: Issues with network configuration, SIP server configuration, or credentials. ## Troubleshooting Steps Here are some steps you can take to resolve the issue: 1. **Check Server Logs**: Examine your server logs for more detailed error messages that might provide clues about what's going wrong. 2. **Verify API Keys and Authentication**: Ensure your API keys are correct and have the proper permissions. 3. **Review Your Request Format**: Make sure your JSON payloads are correctly formatted and all required fields are included. 4. **Check Content-Type Headers**: For PATCH requests, ensure you're including the
"content_type": "application/json"
header.
5. **Implement Error Handling**: Use Vapi's error handling mechanism:
vapi.on("error", (e) => { ... });
to catch and handle errors during calls. 6. **Validate URLs**: Ensure any URLs you're using (like webhook URLs) are correct and accessible. 7. **Review Documentation**: Double-check the Vapi documentation to ensure you're following the correct procedures. Would you be able to share more details about your specific implementation or the complete error message? That would help me provide more targeted assistance. Sources: - [Causes of "400 Bad Request" error in Vapi](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1334142600772456508) - [Troubleshooting steps for "400 Bad Request" error in Vapi](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1336277538267201547) - [Vapi error handling best practices](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1328923059905630238)
b
can you help upgrading my current plan?
k
Email at support@vapi.ai they will upgrade your account.
v
I've escalated your request to upgrade your plan to our support team. They'll be able to help you with the upgrade process and might also be able to determine if your 400 error is related to plan limitations (like concurrency limits). In the meantime, as suggested, you can also email support@vapi.ai directly to initiate the upgrade process. When contacting support, it would be helpful to include: - Your account details - The plan you'd like to upgrade to - The error details you shared earlier This will help our team assist you more efficiently. Is there anything else you need help with while you wait for the support team to reach out? 😊
Hi there! 👋 I don't have any specific information about other issues you might be experiencing, but I'm happy to help with anything else related to your Vapi implementation while you wait for the support team. Based on our previous conversation, I can still assist with troubleshooting the 400 Bad Request error you encountered. If you'd like to share more details about your implementation or have questions about any of the troubleshooting steps I mentioned earlier (like checking server logs, verifying API keys, or reviewing request formats), I'd be glad to provide more guidance. Additionally, if you have any questions about Vapi's features, error handling mechanisms, or best practices for implementation, feel free to ask! Is there anything specific about your Vapi implementation you'd like help with in the meantime?
s
Hi Bryan, I'm looking at the logs and the detailed message is saying 'customer.number' must be a valid phone number in E.164 format including the country code (eg. +15103945339). Please give that a try and let me know what the result is.
2 Views