assistant updates using api do not persist
# support
p
I have an existing assistant and I want to update firstMessageMode to assistant-waits-for-user, the patch request returns an updated config, but if i getassistant it is not reflected. IF I update then go to protal and hit publish and getassistant, still no update seen.
v
@patientdirected It sounds like you're experiencing an issue with updating the
firstMessageMode
for your assistant and having that change reflected in the system. To assist you better, I would need to know if you're making the API call with the correct parameters and if you're following the correct sequence of steps. When you make the PATCH request to update your assistant, ensure that you're including the correct assistant ID and the updated
firstMessageMode
parameter in the request body. After you've received a successful response from the PATCH request, the changes should be saved to your assistant's configuration. However, for the changes to take effect and be reflected when you use
getAssistant
, you might need to publish the assistant. If you've already done this through the portal and still don't see the changes, there might be a delay or an issue with the system. Here's a general sequence of steps you should follow: 1. Make the PATCH request to update the assistant with the new
firstMessageMode
. 2. Ensure you receive a successful response with the updated configuration. 3. Go to the VAPI portal and publish the assistant to apply the changes. 4. Use
getAssistant
to verify that the changes have been reflected. If you've followed these steps and the changes are still not visible, it could be a caching issue or a delay in the system's update process. If the problem persists, please reach out to the support team for further assistance. They will be able to look into the issue more deeply and provide a resolution. Would you like me to guide you through the process of updating your assistant using the API, or do you need assistance with something else?
You can continue this conversation by mentioning me in the message.
p
Turns out to be user error, the key was updated but listed at the bottom of the model object.
wont accept mark as resolved
39 Views