Function Call Key Casing Issue – Snake_Case Being ...
# support
s
Hi Team, I am encountering an issue where VAPI AI is hallucinating snake_case keys (e.g., offboarding_type, first_name) in the function call, even though our API expects PascalCase (e.g., OffboardingType, FirstName). This mismatch is causing 400 Bad Request errors. You can refer to Call ID "726f0efd-00f8-40dc-9889-e6682a01dc0f" where this issue actually occurred. Please look into why the key casing is being altered or misinterpreted despite camelCase being defined in the function schema. Thanks, Sahil
@User can anyone answer this ?
m
Hey! I don't have the ability to view that call yet but I'll loop in @Shubham Bajaj and he can help out a bit when he's on. In the meantime, can you tell me what model you're using for your LLM?
s
it's gpt-4o-mini, also tried with gpt-4o
s
Looking into this now
Just to clarify, you're saying that when you adjust your assistant using Vapi AI it doesn't respect your PascalCase and overwrites it?
s
yes Mason the tools i pass contains the parameters key values in camel or Pascal Case , the bot by default converts it into snake_case that is why i get the 400 Bad Request error while executing the webhook function
s
Thank you for bringing this to our attention, this is definitely something we can improve on this feature. I'll pass your feedback onto the team who is working on this feature.
2 Views