Alexan
04/10/2025, 6:15 PMVapi Support Bot
04/10/2025, 6:17 PMtoolCallId
format. According to the [VAPI documentation](https://docs.vapi.ai/tools/custom-tools), the toolCallId
in your response should match exactly what VAPI sent in the initial request. I notice your toolCallId
includes a "call." prefix (call.vhAIl2pkvzWC80U8k0De1IQR
), which might be causing issues.
Try formatting your response like this:
json
{
"results": [
{
"toolCallId": "vhAIl2pkvzWC80U8k0De1IQR",
"result": "Le rendez-vous est confirmé"
}
]
}
2. **Content-Type Header**: Make sure your webhook is sending the response with the Content-Type: application/json
header. This is required for VAPI to properly process the response.
3. **Troubleshooting Steps**:
- Double-check that the toolCallId
exactly matches what VAPI sent in the initial request
- Verify your server logs to see if there are any errors when processing the webhook
- Try testing the webhook manually using a tool like Postman or cURL
- Check if there are any network issues or firewall settings blocking the communication
Would you like me to provide more specific troubleshooting steps or explain any part of the webhook confirmation process in more detail?
Sources:
- [VAPI webhook confirmation requirements](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1339900285727805513)
- [VAPI webhook response format requirements](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1334658296291921920)Vapi Support Bot
04/10/2025, 6:17 PMVapi Support Bot
04/10/2025, 6:18 PMresults
array containing an object with toolCallId
and result
fields. However, there are several potential issues that could be preventing VAPI from processing it properly:
### 1. Check the toolCallId
format
Make sure the toolCallId
in your response exactly matches the one sent by VAPI in the initial request. According to the [VAPI documentation](https://docs.vapi.ai/tools-calling), the toolCallId
is crucial for VAPI to match the response with the corresponding tool call.
### 2. Verify the JSON structure
Ensure there are no nested JSON objects or unescaped line breaks in your result
field. According to troubleshooting information, the result
field should directly contain the response data as a string without nested JSON.
### 3. Content-Type header
Make sure the content-type of your response is set to application/json
.
### 4. Domain whitelisting
You might need to whitelist vapi.ai
and *.vapi.ai
domains due to dynamic IPs.
### 5. Check server logs and VAPI dashboard
Review your server logs for any errors and check the VAPI dashboard for webhook delivery logs to see if there are any failed attempts and what the reasons might be.
### 6. Test the webhook manually
Try sending a manual POST request to your webhook URL using a tool like Postman or cURL to verify that it's set up correctly and capable of receiving data.
### 7. Case sensitivity
VAPI might be case-sensitive, so ensure that the case of the keys in your JSON response matches the expected format. Some sources suggest webhook bodies have snake_case but real requests have camelCase.Vapi Support Bot
04/10/2025, 6:18 PMusama
04/10/2025, 11:38 PMKyle Brunker
04/11/2025, 7:29 PM