Assistant-request url
# support
c
Over a year ago, I configured inbound calls to trigger an assistant-request to a locally hosted server. This then gets the assistant config, and adds some additional information. This is working great, for all my phone numbers. I need to update the url now, but can not find the correct place to do it. 1. There is no server set for the Phone Number 2. There is no server set for the Assistant 3. There is no server set for the Org Where could this be? I've looked through Dashboard, and API. I was thinking tools, but none of the tools have the url that is being currently used. My only theory is that the url was set on an old depreciated function?.... Any help would be appreciated.
v
To update your assistant-request URL: Go to the [Vapi Dashboard](https://dashboard.vapi.ai/), navigate to your Account page, and look for the Server URL field. Update this field with your new endpoint URL.
Copy code
text
Account > Server URL: https://your_new_server_url
This setting controls the webhook for all inbound assistant-request events when not set at the phone number or assistant level. Source: - [Inbound Support Example](https://docs.vapi.ai/examples/inbound-support)
c
Thanks for the idea autobot, but only Server URL under account is Org settings and there is no server setup.
a
This usually happens when the number was originally tied to an older/deprecated inbound endpoint or an older "assistant-request" callback that isn’t visible in the current dashboard. Do you remember if you set up a custom inbound webhook or routing rule when you first configured it? Some of those older routes still run even if they don’t appear under the new UI. If you want, you can DM me the number setup and I’ll help you trace where the hidden URL is coming from.
c
yes, that is very likely. I've tried using API to pull in phone numbers, assistants, and tools, but can't find the url anywhere.
c
Hi cc_0844, To resolve your issue, it looks like you should update the URL at the account level if no server URL is configured at the phone number or assistant level. Here are the steps to verify and update: 1. Visit the [Vapi Dashboard](https://dashboard.vapi.ai/). 2. Navigate to the Account page. 3. Look for the Server URL field where you can update the URL to your desired endpoint. If no server URLs are set at the phone, assistant, or account levels, as you've mentioned, it might be useful to verify whether there is an older configuration or function that still holds this URL. Since your setup was done over a year ago, it could be linked to a deprecated function or custom routing that might not appear in the current UI. Consider checking any legacy configurations or updates you might have kept, and if everything seems in order, reaching out for a deeper internal check might help identify if there's a hidden configuration handling these calls.
c
Thank you very much for the reply. All those are currently blank and nothing is showing when pulling with API either. What would be the first step to start a deeper internal check for old config?
c
check here for the org level -> then check the phone numbers page and assistant pages. if you cant find anything, please provide a call id where the old URL was used and we will find where its being stored
2 Views