Hello Vapi Support Team,
I'm experiencing a critical issue where my server URL is not being used at all for handling transient assistants. Previously, my setup was working, but after recent changes, Vapi no longer triggers an assistant-request event to my server.
Issue Details
My server URL is correctly set at the account level (as expected for transient assistants).
However, when I call a number without an assigned assistant, Vapi does not send any requests to my server.
There are no errors from my server—it is simply never being used.
The same server URL works perfectly in Postman, responding with a 202 Accepted status.
Troubleshooting Steps Taken
Re-entered and saved the server URL in the dashboard → No effect.
Checked all priority levels (Function, Assistant, Phone Number, Account) → No conflicting server URLs found.
Created a test number without an assigned assistant → Still, no assistant-request event was triggered.
Tested with Webhook.site (a public webhook service) → Vapi never sent any requests.
Reviewed Vapi’s changelog → No clear documentation about changes to transient assistant handling.
Expected Behavior
When calling a number without an assigned assistant, Vapi should send an assistant-request event to my account-level server URL.
My server should then dynamically respond with the assistant configuration.
Current Behavior
No request is sent to my server at all. It appears Vapi is not respecting the account-level server URL.
Request for Support
Can you confirm if Vapi has changed how transient assistants are handled?
Is there a new required setting that needs to be configured?
If this is a bug, when can we expect a fix?
This issue is blocking my production setup, so I’d appreciate an urgent response.
Thank you for your help.