Can't start call on Dashboard
# supporte
Ethan Tan
09/09/2025, 10:00 AMWhen I try to start a call, I get this:
Error
Key doesn't allow origin 'https://dashboard.vapi.ai'.
How do I fix this please?
https://cdn.discordapp.com/attachments/1414913448986284083/1414913450483912775/Screenshot_2025-09-09_at_10.51.36.png?ex=68c14c56&is=68bffad6&hm=74a5c61ea4278e7fc90cf50a2cf25d7b89fb89e6baa85552375d4451b02c98e6&
c
Chiranjeet Mishra
09/11/2025, 7:57 AMCould you please confirm if this is specifically happening with cartesia or other configurations as well?
e
Ethan Tan
09/11/2025, 12:10 PMHi, I'm not using Cartesia, I'm using ElevenLabs for TTS and Deepgram for transcription
c
Chiranjeet Mishra
09/16/2025, 5:16 AMPlease create a new public or private API key and allow all assistants access. Let us know if you continue to experience this issue after the change
e
Ethan Tan
09/27/2025, 5:50 PMThanks Kyle, but how does that key affect the call from the dashboard?
Ethan Tan
09/30/2025, 3:57 PMnudge
c
Chiranjeet Mishra
09/30/2025, 11:27 PMThe API key is used internally to access assistants. If you have an invalid key, the dashboard call wont work. This is an extra security measure to ensure that only valid keys can activate your assistants usage
e
Ethan Tan
10/02/2025, 2:30 PMThanks, Kyle, these are dynamically created assistants when I create a call through the web SDK. So the API key is definitely working
j
John George
10/28/2025, 6:22 PMHow are we supposed to know which API key the dashboard is using?
John George
10/28/2025, 6:40 PMI found the API key the dashboard is trying to use in the request headers in browser tools... it's using one of my restricted production API keys... there doesn't seem to be a way to select the key it uses anywhere so how do I fix this without deleting all my keys and making new ones?
John George
10/28/2025, 6:51 PMfix process was:
1. make new public api key
2. delete vapi.ai cookies from browser
3. reauthenticate
and bingo.
c
Chiranjeet Mishra
11/03/2025, 9:35 PMWe apologize for the delay in responses lately. We are in process of making some changes to our workflow in how we handle support requests. The good news is that we are starting to get back on track of having a 48 hour response time and we would like to start cleaning up anything old.
With that being said, just wanted to check in with you to see if you have made any progress or changes to your project since support has last reached out.
3 Views