Getting a 400 from Custom Tool
# support
a
Hey there I am getting a 400 from a custom tool when its called from the VAPI assistant, if I curl the url manually with the exact body from the webhook log I get the correct expected response.... the error is a blanket 400 with no other context
v
message has been deleted
@Alex Hello! I'm sorry to hear that you're experiencing issues with the custom tool when it's called from the VAPI assistant. It seems like there might be a discrepancy between how the VAPI assistant is sending the request and how your server is expecting to receive it. To assist you better, could you please provide me with the following details: 1. The exact body of the request that you're sending via curl. 2. The configuration details of the custom tool in the VAPI assistant, if possible. This information will help me understand the situation better and guide you towards a resolution. If you're unable to share these details here, please ensure that the content-type and other headers are set correctly in the VAPI assistant configuration, as they can often be a source of such issues.
You can continue this conversation by mentioning me in the message.
s
Hey @Alex can you share the call id?
a
I figured it out there is a discrepancy in the body that is logged in the vapi web hook log as being sent vs what actually gets sent
or at least different marshalling in the body
i.e in the vapi logs the body would contain
toolCalls
, and server logs it was being served
tool_calls
s
We use camel case, you can find the correct types over here: https://api.vapi.ai/api-json#
@Alex can you describer what's broken here?
Hey @Alex because of no respons closing this ticket.
3 Views