Hello guys, I have a question I am using persistent assistants and I am sending some variables via "assistantOverrides"in my backlend so it's not really changing the prompt so if these are changed I dont need to click PUBLISH in vapi Unfortunately some of the settings are i.e turning off the tools so when i PATCH the agent from my backend it does some changes and I have to manually go to VAPI and click PUBLISH. Is there a way to have this via API? So I send the agent via PATCH, then use like API on my backend to do the publish and it will return if status = OK or if there is an error or something? I really do not want to go to vapi each time when I have a small change to click this PUBLISH CTA

Yeah, this is a pretty common friction point when config changes and “publish” are still tied to the dashboard. Usually the cleaner way is to separate your PATCH updates from a proper publish/deploy step through an API flow, so it’s fully backend-driven. I can help you set this up so you don’t ever need to touch the Vapi UI again. Are you working with a single persistent agent, or do you have versioning/drafts enabled? @razz

Hey, I do have Router + 2 agents

That makes more sense. With a Router and 2 persistent agents, I'd first check whether the publish requirement is being triggered by the router, the agents, or both after the PATCH call. There may be a cleaner way to automate the whole update flow so changes go live without needing to hit the dashboard every time. I can help you look into it directly. Let's discuss it privately and see exactly where the publish step is getting stuck in your workflow. @razz