sending wrong data to end call report hook
# support
f
call id: 44d3f5b5-285f-4aa9-8162-120e4a0285cc It says in the webhook request that it sent payload with recording_url but it did send with recordingUrl. Why is this ambiguity ?
@User
v
You can continue this conversation by mentioning me in the message.
@flake9 I apologize for any confusion caused by the discrepancy in the payload naming. It's possible that there was a change in the naming convention or a documentation error that led to this ambiguity. To ensure consistency and avoid such issues in the future, it would be best to update the webhook documentation or the payload structure to match. If you have control over the webhook provider, you might want to standardize the naming convention used for the payload properties. If you are a consumer of the webhook, you may need to adjust your system to accept both
recording_url
and
recordingUrl
or reach out to the provider for clarification. If you need further assistance with this issue or if there's anything else I can help you with, please let me know.
Got it. Tagging @User for additional help.
f
@User
@Sahil
@User
@User
@Shubham Bajaj
f
In the webhook request payload
On vapi dashboard
under my VAPI - Logs - webhooks - webhook - Body its snake case but the request i received was in camel case
s
We send data in camelCase to your server payload. @flake9 can i close this ticket now if your doubts are resolved?
f
yrs it is but why is it in snake case in VAPI - Logs - webhooks - webhook - Body Isnt it should be in camel case there as well ?
Also @Shubham Bajaj Can you please check this one ? https://discord.com/channels/1211482211119796234/1313143048170897408/1313143048170897408 It seems to be a bug
s
Yeah those logs requires parsing!!
f
can that be added as bug ?
we can close this one! THanks