Getting unexpected payload for my tool calls, assi...
# support
j
For some reason I am getting all the field keys in snake case instead of camelCase. Here is an example tool call ID -
call_dfgxvo2LaQakpvwNpF5c0orQ
and the call ID for the same tool call -
593f23b6-d36e-4f76-8e90-261e40416a74
. As an example, in the tool call body I was expecting
toolCallList
but got
tool_call_list
instead
v
You can continue this conversation by mentioning me in the message.
@jit I understand that you're experiencing an issue with the casing of the field keys in the API response. It seems like there might be a discrepancy between the expected format and what you're receiving. To assist you better, could you please provide me with more details about the specific tool or API endpoint you're using? This will help me understand if there's a setting or parameter that can be adjusted to return the keys in camelCase as you expect.
j
I am using the function tool @Vapi
v
@jit Thank you for clarifying that you are using the function tool. It seems like there might be an inconsistency in the response format you're receiving. Typically, the casing of the keys in the response should match the expected format as per the tool's documentation or the API's design. If the tool's documentation specifies that the response should be in camelCase and you're receiving snake_case, this could be a configuration issue or a bug. Unfortunately, I don't have the ability to directly check the tool's configuration or the specific call you mentioned. However, I can guide you on how to report this issue to the support team so they can investigate further. Would you like to proceed with reporting this issue?
j
@User
s
@jit i have looked into the tool call and we are not sending any of parameters in snake case. for reference your tool call name is c6fce57b-a6c5-431f-aa7b-b8976136a6ad.
3 Views