The server url won’t save its own your side. It actually shows as saved but it doesn’t use it for webhook post. I found out because it was using the server url in my account vs the assistant even though it showed its bypassing it. So when making an outbound call with this assistant it used the higher level account url and sent the webhook data to theburl that was saved in the account but when making an inbound call to the assistant it used the correct url that was saved to the assistant vs the account level. Also when I try to delete the account server URL it won’t allow null

Suggestion: Double-check that your assistant's server URL is set with the correct priority and includes a

credentialId

for authentication. You can update the assistant's server URL using the API like this:

json
{
  "server": {
    "url": "https://your-server.com/webhook",
    "credentialId": "cred_abc123"
  }
}

After updating, test a webhook event to confirm it's hitting the correct endpoint. If it still uses the account-level URL, ensure no function or phone number server URL is overriding it, as these have higher precedence ([documentation](https://docs.vapi.ai/server-url/setting-server-urls)). Sources: - [Setting server URLs](https://docs.vapi.ai/server-url/setting-server-urls) - [Server authentication](https://docs.vapi.ai/server-url/server-authentication)

Hi Garret (eWebify), If you're trying to save a server URL and experiencing issues, ensure you're using the correct precedence order, as messages and server configurations are based on this. For “tool-calls” messages, the server URL is determined by these priorities: 1.

tool.server.url

(if configured) 2.

assistant.serverUrl

(if configured) 3.

phoneNumber.serverUrl

(if configured) 4.

org.serverUrl

(if configured) Verify that your server is set according to these configurations to ensure proper setup [as detailed in the API reference](https://docs.vapi.ai/api-reference/webhooks/server-message). If you're dealing with voicemail configurations, refer to the documentation on configuring voicemail detection with the new VapiVoicemailDetectionPlan [here](https://docs.vapi.ai/changelog/2025/4/30). For any deprecated components, such as the SmsSendTool now being renamed to SmsTool, ensure your configurations are updated accordingly [as per this changelog](https://docs.vapi.ai/changelog/2025/5/19). If further assistance is needed, I recommend checking these configurations against your current setup to identify discrepancies.

Ummm so I am doing it right it just isn’t saving. Are there known errors around this?

Is this the serverUrl on the assistant level or the org level? Either way, we can override it on our end if needed as a workaround. Let us know how you would like to proceed

It is on the assistant level and it works and recognizes it when calling into the phone number that is assigned to the assistant but when it is an outbound call it isn’t using that ServerURL instead it defaults to the account wide one.

If you are able to switch the org level one to the assistant one then delete it on the assistant level, that could be another workaround.