When we call VAPI Assistant is starts talking using a different provider and voice_id that was set up by us. Looks like VAPI replaces the provider to its defaults: playht and voice_id to jennifer. During the investigation we accidentally found out that PATCH overrides all assistant settings. We are not sure if it has anything to do with our issue, but it looks kinda similar. Please, note that we do not call PATCH during our calls. This is the initial assistant settings. Note that the voice_provider is 11labs:

GET /assistant/091ae3e9-0537-479d-9f83-8c25dd7c50ba
RESPONSE BODY:
{..., 'voice': {'model': 'eleven_turbo_v2', 'voiceId': 'QrRJx7pPvPGFVMtAx4IR', 'provider': '11labs'...}

Then we patch the responseDelaySeconds attribute and provider is now changed:

PATCH /assistant/091ae3e9-0537-479d-9f83-8c25dd7c50ba
REQUEST BODY:
{'responseDelaySeconds': 0.15}

RESPONSE BODY:
{..., 'voice': {'voiceId': 's3://voice-cloning-zero-shot/801a663f-efd0-4254-98d0-5c175514c3e8/jennifer/manifest.json', 'provider': 'playht'...}

message has been deleted

@Vapi Our issue is not with the PATH request itself. The PATCH overriding unspecified attributes was an accidental discovery we made during our investigation. I mentioned it in the post because I think it might be relevant to our issue. Which is that the provider and voice_id get changed on VAPI side without us doing anything. We just call an Assistant and all of a sudden it speaks in a different voice that was set up by us. We check the settings and they are different from what we set up. This is the problem, not the PATCH request itself.

@Rupasov I apologize for the confusion earlier. It seems like there might be an issue with the VAPI system where the voice provider and voice_id settings are being changed unexpectedly. This is certainly not the intended behavior, as your settings should remain consistent across calls unless explicitly changed by you. To address this issue, I would recommend the following steps: 1. Document the instances when the voice provider and voice_id change unexpectedly, including any relevant logs or details about the calls made. 2. Verify that there are no other parts of your system or team members that might be making changes to the assistant settings. 3. Reach out to VAPI support with the information you've gathered to help them understand and troubleshoot the problem. Since this seems to be an issue on the VAPI side, their support team will be best equipped to help you resolve it. They may need to investigate their systems to determine why these changes are occurring without your intervention. If you need any further assistance or if there's anything else I can do to help you with this matter, please let me know.

Confirmed this was an issue with PATCH in the morning. Sorry about that.