This error is specifically with this one organisation profile and account. When I try logging in with this account with a username and password, I get a never ending ID verification process. But when I log into this account with my google credentials, I can log in but no new agents I create can be called from the VAPI dashboard. I've seen others comments saying to check the public keys, but for one I have, and 2, they are not needed when trying to call within the dashboard or VAPI demo page - something I need for a potential client who I'm worried of losing now since they fear the solution doesn't work! I need this resolved asap! And in resolving the verification process on my account, this might fix this issue too? https://cdn.discordapp.com/attachments/1416007038110269521/1416007038403739702/image.png?ex=68c546d2&is=68c3f552&hm=0dd42efcaa133e5ea8230a44e391da0f8aed6dad527e7d8c5028d8559132693d&

Hi Hazza, If you're experiencing issues with an assistant ID due to key-related problems, you should ensure that the correct credentials are being used, as discrepancies between private and public keys can lead to such issues. Refer to the documentation on session creation to correctly configure your assistant ID: 1. Ensure you have the correct

assistantId

when making API requests. 2. Verify that your authentication token is valid and specified in the format

Bearer <token>

. 3. If using a

session

, include the details correctly in your request as mentioned [here](https://docs.vapi.ai/api-reference/sessions/get). If the issue persists, can you give any potential errors in your dashboard under Call Logs for more detailed insights.

I have spoken to someone else who had the issue and have gotten to the bottom of it. https://discord.com/channels/1211482211119796234/1414603454839656538/1414844581878562856 It seems that when I created a new public key, that same key is used by default for every new agent created after it! And that new public key was restricted to one agent, therefore it failed for every other agent made after it.

I am facing this problem purely on the Vapi interface. I don't understand how this can be. If I create a blank agent and just click "call" to test it I get this error. Why?

Yep exactly the same thing as me. I think im going to have to resort to doing the same!

Up... we're getting an error about ORIGIN

For the error about ORIGIN, could you share a screenshot of the error?

You will have to add another private or public API VAPI key instead of editing the active key. Once you create it, it will work on the UI

Doesn't work

There shouldn't be. Please let us know if you encounter this issue again