I built a voice agent on vapi and have set up 2 automations on make.com to run it. Automation 1: Sends an api call to vapi to GET request data and triggers calls. Automation 2: This is triggered when the call is completed and the end of call report is generated, here Vapi POST request onto my Web Hook, and sends the data. Now the issue here is i recently added a new webhook link to my Vapi Agent (Published it and saved it as well) However when i make GET request API calls to my agent through the first automation, or even just a GET request using postman or curl, it retrieves the old webhook URL not the new latest updated and published one. Also when i run the agent directly through the Vapi web app it works and the latest webhook itself is called, so the issue I'm assuming is purely with the API. i am not aware why the API is still giving older version data, is this an issue on my end or just a bug? Anything i can do to fix this?

This issue is likely due to API caching or propagation delay, though your updated webhook works via the web, the API still returns old data; try re-publishing with a minor change to force a refreh..

I republished with changes to the prompt, when i made an api call again, the changes to the prompt reflected but the changes to the server URL for the webhook still didnt occur.

Try making and publishing a minor assistant update to force a refresh, as caching or propagation delay may be causing the issue

I have made minor prompt changes, token number changes, advanced setting changes and published it. All of them update when i make an API call, all except for the webhook. Should I be reporting a bug?

Hey, really sorry for your experience. If possible, could you record a loom video describing this error/behavior or inconsistency in the dashboard with the steps to reproduce it? That way, I can share this with my team, and we'll take a look. We'll even try to reproduce the same so we can fix it for you. Also, I'll request you to share your assistant ID.

Thank you the vapi support team has resolved it. Turns out the webhook field had been edited in the backend for the vapi API. Since mine was a legacy agent it had the older infrastructure and hence didnt update. Now its fixed no worries.

This ticket has been marked as solved, and as a result, you will no longer receive any further responses. Kindly create a new support ticket to escalate your inquiry.