While triggering the tool calls the variable which iam using are getting formated. for example iam using variable name as shipmentId but iam seeing in webhook logs like shipment_id. it was seanding shipment_id instead of shipmentID.

Hi there! 👋 I understand your confusion about variable formatting in webhook logs. I can explain what's happening with your

shipmentId

variable. According to the information I found, this is actually expected behavior in Vapi. [Vapi webhook logs use snake_case for variable names, while server logs use camelCase](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1341204221826957432). This means that when you define a variable as

shipmentId

in your code, it will appear as

shipment_id

in the webhook logs. This discrepancy between naming conventions can cause confusion when debugging or testing. As noted in the documentation, some users have spent significant time troubleshooting this issue, especially when trying to copy and paste bodies from webhook logs for use in test cases, as they need to convert the request body back to camelCase first. Unfortunately, based on the information available, there doesn't appear to be a built-in configuration option to control this formatting behavior. Some users have implemented custom transformer functions on their own servers to transform the payload into their required format. Is there anything else you'd like to know about handling variables in Vapi? Source: - [Discord Thread about Webhook Bodies](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1341204221826957432)

@User but iam getting the snake case to my server.

Hey! To help track down this issue, could you share: - The call ID - When exactly this happened (the timestamp) - What response you expected to get - What response you actually got instead This would really help us figure out what went wrong!