I'm trying to create a Scenario in Make.com where it reads columns from a Google Sheet and then will call numbers from the sheet with Vapi. This was following a Youtube Video It intermittently will make the call, however in Make.com it marks an 400 Error. I want to make sure this is as seemless as possible prior to sending out calls, as well as wanting to offer this to my clients. 1. The phone numbers have the +1 for the country code in them. (Which I was advised to make sure they had this) 2. API Keys, Assistant Keys, and Phone Keys have been triple checked. 3. Rebuilt this scenario as well as using a JSON blueprint provided. Any help to troubleshoot this. https://cdn.discordapp.com/attachments/1347624655216971796/1347624655766290572/screencapture-us2-make-547022-scenarios-1163849-edit-2025-03-07-10_36_55.png?ex=67cc80c3&is=67cb2f43&hm=517634794d1a25499c65de7a4ec79116dde8e16fb93768216fba55e10fc664ec&

Hi there! I see you're having trouble with 400 Bad Request errors when integrating Vapi with Make.com. Let me help you troubleshoot this issue 🔍 Based on the information you've provided and common issues I've found in our documentation, here are some potential causes and solutions: ### Common Causes of 400 Bad Request Errors: 1. **Incorrect Payload Structure**: - Make sure you're not including unexpected fields in your API request - Remove any fields not expected by the endpoint (like

credentials

if not required) - Follow this example structure for call requests:

json
   {
     "assistantId": "your-assistant-id",
     "assistantOverrides": {
       "variableValues": {
         "name": "John"
       }
     },
     "customer": {
       "number": "+1xxxxxx"
     },
     "phoneNumberId": "your-phone-id"
   }

[source](https://docs.vapi.ai/assistants/dynamic-variables) 2. **Concurrency Limit Issues**: - You might be exceeding the allowed number of concurrent API calls - Consider implementing a queueing mechanism or adjusting your scenario to space out calls [source](https://discord.com/channels/1211482211119796234/1211483291191083018/1334142600772456508) 3. **API Endpoint Configuration**: - Ensure you're using the correct endpoint:

https://api.vapi.ai/call

- Verify your authentication headers are properly formatted:

Authorization: Bearer YOUR_API_KEY

[source](https://docs.vapi.ai/api-reference/calls/create) 4. **Invalid Assistant ID Format**: - I noticed in your screenshot that your Assistant ID appears to be missing a character (should be 36 characters in UUID format) - Double-check that your Assistant ID is correctly copied from the Vapi dashboard Since the error occurs intermittently, it might also be related to rate limiting or temporary service issues. Would you be able to share the exact JSON payload you're sending (with sensitive info redacted)? That would help me provide more specific guidance.

this is how iam doing it, may be it helps https://cdn.discordapp.com/attachments/1347624655216971796/1347662845256532099/image.png?ex=67cca454&is=67cb52d4&hm=1754bc7c3dd5412d3c239ef7eab4ea9dc5055bacda2ceaa634e15fb3cac5a6c1&

I've heard the HTTP version to work - I'm very new to Make.com, so learning all this on the fly setting it up. Is there a youtube video I can perhaps follow for this kind of set up?

Hey @Lauren.WildSpiritDev checking if this is resolved for you.

hey lauren @Lauren.WildSpiritDev please I set you a request, please accept, our scenario set up in make is exactly the same, i just want to ask a few questions