ANOTHER BREAKING CHANGE VAPI!!!
# support
l
Hello @Vapi team, We noticed that requests made to the /call API have suddenly started failing. Upon reviewing the logs, it seems there might have been a breaking change introduced in the /calls API. This is the second breaking change in just one week without any notice, and it is having a significant impact on the stability and reliability of the product. Could you please share if there are any plans to notify consumers in advance of breaking changes? A warning or heads-up before implementing such changes would be greatly appreciated to help mitigate these issues. Thank you for your attention to this matter, and I hope we can avoid similar disruptions moving forward. @Vapi Incident !!!!
v
Based on the information I found, I can see that the
/call
and
/calls
APIs in Vapi are related and include similar endpoints for managing calls. While I don't have specific information about Vapi's advance notification policy for breaking changes, I found that Vapi maintains a [changelog](https://docs.vapi.ai/changelog) that documents updates to their services. For immediate assistance with your API failures, I recommend contacting Vapi support directly as they can provide guidance on your current setup and any necessary migration steps. Sources: - [Vapi Changelog](https://docs.vapi.ai/changelog) - [Discord Support Channel](https://discord.com/channels/1211482211119796234/1334660289668583514)
k
Same here I also reported the same incident as the websockets are failing and it was working fine till yesterday
@Leo Did you send an email to support? As I have sent and got a reply but, not helpful as of now may be later this discussion will end to some positive conclusion
l
About this one specifically. It looks the breaking change was reverted yesterday
k
Which means your issue has resolved already.
l
Yes. But IDK for how long. We tried to fix it on our end, but since they reverted the change. We couldn't apply the hotfix. Our case was: Old Version: If we provide some field in the request, Vapi rejects the body, so we cannot put these properties in the payload New version: The field that Vapi rejected in the old version became required. So, hotfixing it requires sending the new properties. But if we send the fields and Vapi rolled back, our requests will fail because Vapi will reject the payload because we submit these properties 😕
v
Message marked as helpful by @Rohan! 🎉
p
checking if this is resolved/solved for you?