Hi, First I had a error where I get "**Key Doesn't Allow AssistantID**" then i removed all my API-KEYS and now I get this. I did refresh, hard refresh, waited for sometime, nothing happened. How can I fix this issue? When I get this? When trying to make a web call for testing. Is it on all Assistants? Yes, on all assistants. https://cdn.discordapp.com/attachments/1412794371824160878/1412794372113698937/image.png?ex=68b996ca&is=68b8454a&hm=d34813b132d60db7f284cec5ddba5f4d4b570f225779a6a15f796019fdf55db0&

Suggestion: Since removing all your API keys may have disabled your assistants' ability to make web calls, try re-adding a valid API key with the correct permissions for your Assistant IDs. After adding the key, refresh the page and attempt your test call again. If the issue persists, double-check that your Assistant ID and Phone Number ID are correctly set in your configuration, as missing or incorrect values can prevent the service from working ([source](https://discord.com/channels/1211482211119796234/1370485222214336564)). Source: - [Vapi Discord Support Agent not speaking and configuration issues](https://discord.com/channels/1211482211119796234/1370485222214336564)

I added 1 Private and 1 Public API key, selecting the Assistant, it did not work

Message marked as helpful by @gklptrgt! 🎉

May I learn what causes this issue and how to overcome, because I connect my Agents with API to website to see details there.

I'm getting the "key doesn't allow assistantid" error when I try to use the "talk to assistant button" for all of my assistants. I've changed nothing about my configuration. This is something on VAPI's end. The only new thing is that I needed VAPI support's help bypassing the ID check to login yesterday.

@Keith I fixed this issue with deleting all my API then creating new ones for Specific Assistant, I don't know whats the cause and waiting to learn more about it.