Hello, I'm trying to create a post request for one of my outbound voice agents, however, when I try to create the request through vapi, it limits the amount of characters I can put into customer.number field to only 3 characters. I'm not sure how to get around this, as I need more than 3 characters to actually insert the full phone number. I tried testing this on postman, and it was successful and I got a phone call from my voice agent, however, using the exact same json code inside of vapi doesn't work, as my customer.number field is only limited to 3 characters, if anyone could help me fix this that would be very much appreciated! As I'm trying to make this work for a make.com http request module. Thank you so much! https://cdn.discordapp.com/attachments/1307132924822425661/1307132925166489712/Postman_Call_Example.png?ex=673931e6&is=6737e066&hm=0439cf5a5cbbb358e28cf57e7ed92a01507810292c825ffcd3a860c44988fcf1& https://cdn.discordapp.com/attachments/1307132924822425661/1307132925954756689/Vapi_POST_Create_Call_Error.png?ex=673931e6&is=6737e066&hm=525906c6ee2e5e6d479ef47e03730090c70cd48c5d20f7dfa45f8426b9eea8ab&

@Ali M Hello! It sounds like you're encountering a limitation within the VAPI interface that's preventing you from entering the full phone number. This could be a bug or a misconfiguration in the VAPI system. Since you've confirmed that the request works correctly in Postman, the JSON structure and the API endpoint are likely correct. To resolve this issue, I would recommend reaching out to the VAPI support team to report this limitation. They should be able to provide guidance on whether this is a known issue and offer a solution or workaround. In the meantime, if you're trying to integrate this with make.com (formerly Integromat), you might want to use the HTTP request module within make.com to bypass the VAPI interface limitation. You can set up the HTTP request with the correct JSON payload as you did in Postman. If you need further assistance with setting up the HTTP request in make.com or if you have any other questions, please let me know!

So with the make.com scenario, Ill put a screenshot of what I currently have, but basically Ive used a HTTP make a request module, and essentially copied over the correct parameters from postman. However, I get this error message when I try to run the scenario. This error I'm honestly not sure what I've done wrong, maybe it's my formatting or the variables Ive put in, but for context, the airtable value thats being searched and put through the aggregator is just my phone number in the correct country code. So i really don't know what the error could be to be honest. https://cdn.discordapp.com/attachments/1307132924822425661/1307138743324643328/image.png?ex=67393751&is=6737e5d1&hm=7356feb650ef08894ddbcc85c23f35cd7479214b3906b02fabfea4b3280de396& https://cdn.discordapp.com/attachments/1307132924822425661/1307138743609851954/image.png?ex=67393751&is=6737e5d1&hm=47e83126311618d49476142a71f4206f248a58cb03b9839585ae04908e5389ce& https://cdn.discordapp.com/attachments/1307132924822425661/1307138743873962035/image.png?ex=67393752&is=6737e5d2&hm=b3e81ace850465fd441b6bd6f3f5818f051423fc32af92455b0208054c6bb338& https://cdn.discordapp.com/attachments/1307132924822425661/1307138744125755422/image.png?ex=67393752&is=6737e5d2&hm=83ceee3b374588fa33cffa543558bde1c4089ea2c3fc8fbe68536b3f2ca6d9e4&

@Ali M I'm glad to assist you with the make.com scenario. However, without the actual screenshot or error message, it's a bit challenging to diagnose the problem precisely. Could you please provide me with the error message you're receiving or describe the issue in more detail? In general, when setting up an HTTP request in make.com, you'll want to ensure the following: 1. The URL is correct and corresponds to the VAPI endpoint you're trying to reach. 2. The HTTP method is set to POST if you're creating a new request. 3. Headers are properly set, including

Content-Type

as

application/json

if you're sending a JSON payload. 4. The body of the request is formatted correctly as JSON and includes all required fields. 5. Authentication is correctly configured, whether it's via API key, OAuth, or another method. If you're seeing an error, it could be related to any of these factors or something specific to the data you're passing through. If you can provide the error message or more context, I'll do my best to help you troubleshoot the issue.

the error message is [DataError Error: 400 Bad Request failed to extract key for request id 75e20228-fa25-4118-83dd-de7ca9d7e424] @Vapi

@Ali M A

400 Bad Request

error typically indicates that the server cannot process the request due to a client error, such as incorrect syntax or invalid request message framing. The specific message "failed to extract key for request id" suggests that there might be an issue with the API key or the way it's being sent in the request. Here are a few steps you can take to troubleshoot this issue: 1. **Check API Key**: Ensure that you have included the correct API key in the headers of your HTTP request. The API key should be provided in the format expected by the VAPI, usually as a header. 2. **Headers**: Verify that all required headers are included in your request. For VAPI, you typically need to set the

Authorization

header with your API key. 3. **Request Body**: Make sure that the body of your request is properly formatted as JSON and includes all the necessary fields. If you're sending a file, ensure that the

Content-Type

is set to

multipart/form-data

. 4. **Endpoint URL**: Confirm that the URL you're using is correct and corresponds to the VAPI endpoint for creating a post request. 5. **Permissions**: Check if the API key has the necessary permissions to perform the action you're trying to execute. 6. **Documentation**: Refer to the VAPI documentation to ensure that your request structure matches the expected format. If you've verified all of the above and the issue persists, it may be necessary to contact VAPI support for further assistance. They can provide more detailed information on why the key extraction is failing for your request ID.

ah wait i fixed it, i just needed to add content type as a header thank you!

@Ali M Sweet. Have a great day!