Milan
03/11/2025, 9:09 PMVapi Support Bot
03/11/2025, 9:11 PMtoolCallId
(camelCase), but in Image 4, the logs show tool_call_id
(snake_case). According to Vapi's documentation, the correct format should be toolCallId
in camelCase.
Here's the exact format Vapi expects:
json
{
"results": [
{
"toolCallId": "YOUR_TOOL_CALL_ID",
"result": "Your result message"
}
]
}
Even though your webhook is returning a 200 status code and shows as "accepted" in some logs, the inconsistent field naming could be causing Vapi to fail when processing the response.
Common reasons for this type of issue include:
1. Mismatched toolCallId
that doesn't match the one sent by Vapi in the initial request
2. Incorrect JSON formatting (camelCase vs snake_case)
3. Content-Type header issues (though yours appears correct with application/json)
I recommend updating your webhook to consistently use the camelCase format (toolCallId
) and ensure it exactly matches the ID provided by Vapi in the request.
If the issue persists after making these changes, please share the actual error message your assistant is returning, which would help with further troubleshooting.
Sources:
- [Discord message about JSON structure](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1341204221826957432)
- [Discord message about toolCallId matching](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1325000684231196775)
- [Discord message about JSON formatting](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1334658296291921920)Milan
03/11/2025, 9:47 PMMilan
03/11/2025, 10:23 PMMilan
03/12/2025, 6:09 PMKings Big
03/12/2025, 8:31 PMMilan
03/13/2025, 12:29 PMMilan
03/13/2025, 12:29 PMKings Big
03/16/2025, 10:36 AM