org server URL
# support
@Tim
3 days now
m
This is absolutely terrible. Same here
r
I created an authentication and it worked but stopped using MAKE
m
Okay guys got a workaround for now. Instead of setting the Server URL on a global level set in within the specific voice assistant. Under advanced, there is a dropdown called "Messaging", set your url there. @TeamVapi You need to work on your support.
f
This doesn't work for inbound calls
r
I have been able to update/set, seems they are requiring authentication now
c
Hi Ron, To resolve your error after updating the software, please ensure that you're using the correct server URL for your organization. You can now specify a server URL to receive webhook callbacks for workflow events directly, as detailed in the [June 13, 2025 changelog](https://docs.vapi.ai/changelog/2025/6/13). If the issue persists, review your settings related to the integration and workflow models, ensuring the configuration aligns with your current setup requirements. If you've recently changed other settings like the voice provider or any deprecated properties, ensure the changes comply with the latest updates, such as removing the
codeSwitchingEnabled
from Deepgram transcriber configurations. You can find more information in the [June 24, 2025 changelog](https://docs.vapi.ai/changelog/2025/6/24). I hope this helps resolve your issue. If this doesn’t resolve the issue, please let us know and we’ll be happy to step in and assist further.
r
Your reply doesn't align with the issue
the issue is saving the URL in your interface
it seems to require now authentication which it did not in the past, at a minimum the error message should be a little more descriptive
c
Hello, We sincerely appreciate your understanding and apologize for the inconvenience this has caused. Our team is currently investigating the matter to determine the root cause and implement a resolution as quickly as possible. We will provide you with updates as soon as new information becomes available, and we remain committed to ensuring this issue is fully resolved
r
just close this, nobody seems interested
and i found the resolutin
c
Hello, Sorry for the inconvenience and thanks for your patience. Don’t hesitate to contact us again let us know if you need further assistance.
2 Views