Production issue when creating new Assistants in V...
# support
h
v
The 403 error "Key doesn't allow assistantId ..." means your API key does not have permission to access the specified assistant. To resolve this, go to the [Vapi Dashboard API Keys page](https://dashboard.vapi.ai/keys), locate your API key, and ensure it is either organization-wide or explicitly allowed to access the assistantId in question. Example: 1. Navigate to Dashboard → API Keys. 2. Edit your API key and check its allowed assistant IDs or set it to "All Assistants" if appropriate. This should resolve the authorization issue for new assistants. Source: - [Server Authentication Vapi Docs](https://docs.vapi.ai/server-url/server-authentication)
c
Hi, please follow the below steps: First Step: Go to the VAPI dashboard Second Step: Go to the API Keys page Third Step: Scroll down to the Public Keys section Fourth Step: Select the default public key Fifth Step: Remove allowed assistant IDs, origins,  allow transient assistants Sixth Step: Do a hard refresh Seventh Step: Try again making a call.
h
Hi Aditya, I checked in VAPI this procedure and it seems it the API keys do not have an Edit option as per screenshot below: It seems I would need to create a new API key and apply the config that you mentioned above? https://cdn.discordapp.com/attachments/1415182340711514243/1422086177640415233/Screenshot_2025-09-29_at_3.01.45_pm.png?ex=68db6475&is=68da12f5&hm=5bb112a7d8014abbe442a04b90dbf794c21b32e8ed1a50ff1be99f700296727d&
c
Yes, once you add a new key it should work
3 Views