Any new Assistants I make don't work in the main V...
# support
b
Any new Assistants I create don't work when I click, "Talk to Assistant". Instead it throws the error attached that says, "Key doesn't allow Assistant ID "######"". The issue started at the same time Vapi started their KYC issue whenever we would make an outbound call with their platform. https://cdn.discordapp.com/attachments/1425196626825445438/1425196627739672678/Error_Vapi.png?ex=68e6b54a&is=68e563ca&hm=4ea3c994224e3563cc07bd1d2a7ccfa25f84bd81869d0ec632959960dc6ff15b&
v
To resolve the "Key doesn't allow assistantId" error, generate a new JWT token that explicitly includes your new Assistant's ID in the
allowedAssistantIds
restriction.
Here's a code snippet for the payload:
Copy code
js
const payload = {
  orgId: 'your-org-id',
  token: {
    tag: "public",
    restrictions: {
      enabled: true,
      allowedAssistantIds: ["your-new-assistant-id"],
      // ...other restrictions
    }
  }
};
// Sign this payload with your private key to create the JWT.
After generating the new token, use it in your Vapi UI or API requests. For more details, see the [JWT Authentication guide](https://docs.vapi.ai/customization/jwt-authentication). Source: - [JWT Authentication](https://docs.vapi.ai/customization/jwt-authentication)
b
The error is occuring in the Vapi dashboard in the Assistants section.
g
Try Reloading the tab after following the vapi bot instructions
c
Please create a new public/private API key in the VAPI API keys section and it will resolve this issue
b
That worked! Thanks!
c
Glad you were able to get this resolved. We’ve closed this ticket, but your input is very valuable to us. Please take a moment to complete the survey, which should appear in a couple of days—your feedback directly helps us improve our support.
2 Views