When trying to add my azure openai credentials i always get this response. {"message":"Couldn't Validate Azure OpenAI Credential. Error: The API deployment for this resource does not exist. If you created the deployment within the last 5 minutes, please wait a moment and try again.","error":"Bad Request","statusCode":400}% The endpoint works, the model works, and the API key works just fine if i just use python to test it. Using this curl. of course with my information. curl --location 'https://api.vapi.ai/credential' \ --header 'accept: */*' \ --header 'accept-language: en-GB,en-US;q=0.9,en;q=0.8' \ --header 'authorization: Bearer MYAPIKEYHERE' \ --header 'content-type: application/json' \ --header 'origin: https://dashboard.vapi.ai' \ --header 'priority: u=1, i' \ --header 'referer: https://dashboard.vapi.ai/' \ --header 'x-dashboard-version: 5334a312820225a5d26aa779a05c4441a0178223' \ --header 'Cookie: _cfuvid=CUSErOTQze7IfYksWMA7yAByAUDG7qgz41gjoqw2vwU-1737501475592-0.0.1.1-604800000' \ --data '{ "provider": "azure-openai", "models": [ "insert-your-model-name-here" ], "region": "insert-your-region-here", "openAIEndpoint": "insert-your-openaiEndpoint-here", "openAIKey": "insert-your-openAIKey-here" }'

Can you send a screenshot of your deployed model name?

gpt-4o (version:2024-08-06)

ccing: @Sahil

I think i solved it by mistake, the endpoint should go up to -- chat/completions?api-version= -- without the version, up to the equal lol, this is the weirdest thing ever .

You will need to use the OpenAI as your provider.

what does this mean?

Hey, so basically you will need to have the model name same as openai provider standard like gpt-4o not gpt-4o-xyz.

would this work? and quick question, how would this look in the assistant creationg model key, if this deployment is correct.? https://cdn.discordapp.com/attachments/1338649953102463038/1340365447752581242/image.png?ex=67b21819&is=67b0c699&hm=07abe6853ee700cba3e4a203cf91b4b1b6cc11dc685b2ad517f3cc810b33211b&

yup, this should work

well the curl is not accepting the credentials again. @Sahil