Duplicated assistant uses wrong webhook settings
# support
v
To fix the webhook settings for your duplicated assistant, update its server URL to the correct endpoint. You can do this via the API with the following example:
Copy code
bash
curl -X PATCH https://api.vapi.ai/assistant/{new_assistant_id} \
  -H "Authorization: Bearer <token>" \
  -H "Content-Type: application/json" \
  -d '{"server": {"url": "https://your-new-server.com/webhook"}}'
This will ensure webhook events are sent to the right server for your new assistant. Tip: Always verify and update webhook settings after duplicating an assistant to avoid inherited configurations. [See more in the docs](https://docs.vapi.ai/server-url/setting-server-urls) Sources: - [Setting Server URLs](https://docs.vapi.ai/server-url/setting-server-urls) - [Update Assistant API Reference](https://docs.vapi.ai/api-reference/assistants/update?explorer=true)
f
The server url is correct in the assistant config
Seems like an issue on vapi's backend that I can't see
Call ID example where the webhook data was sent through the wrong configuration: 8c453f69-a49c-4a09-b39b-e2205b5c6797
k
Can you provide the correct webhook link? Also, can you try to patch it via API? ^^
f
The correct webhook link is already in the config of the assistant, and yes I have to tried to patch via API
The issue is that from everything I see it's conifgured correctly
It's specifically when I call the phone number that the assistant is attached to. I can DM you the server url if needed, I'd rather not post it publicly
Figured it out, you can close this one
k
Marking this ticket as Solved ✅