https://vapi.ai/ logo
Join Discord
Powered by
Key doesn't allow AssistantID? I have created my t...
# support
s
I keep getting an error when trying to connect to the assistant on a demo voice call through the web app. But it's just saying the assistantID is not allowed. I checked my api keys and none of it is restricting usage. What's going on?
v
@SlaviSavanovic I'm sorry to hear that you're experiencing issues with connecting to the assistant. It sounds like there might be a problem with the assistant ID you are using. To assist you better, could you please provide me with the assistant ID you're trying to use? This will help me to check if there's any issue with the ID itself or if there's another underlying problem that we need to address.
You can continue this conversation by mentioning me in the message.
s
5b3404cd-bbec-4502-b263-378769188a35 -> thius is the one but I tried creating multiple assisants andd none of them worked. Only the first couple I made work
@Vapi
v
@SlaviSavanovic Thank you for providing the assistant ID. It's possible that there might be an issue with the newer assistant IDs you've created. Since the first couple of assistants you made are working fine, it could be a problem with the system not recognizing or allowing the new IDs. To resolve this, I would recommend the following steps: 1. Double-check that the assistant ID is correctly entered in your web app's configuration. 2. Ensure that there are no restrictions on the new assistant IDs in your Voice API settings. 3. If the issue persists, it might be necessary to look into the system logs or contact the technical support team for a deeper investigation. If you've already verified the first two steps and need further assistance, please let me know, and I can guide you on how to proceed or escalate this to the technical support team if necessary.
s
It's not my web app. it's vapi's web app. there is a button that says call assistant, acting as a demo @Vapi
v
@SlaviSavanovic I apologize for the confusion. If you're using VAPI's web app and the "Call Assistant" demo feature is not working with the new assistant IDs, it seems like there might be an issue on the VAPI platform side. Here's what I suggest: 1. Ensure that the assistant IDs you're trying to use are active and properly configured in your VAPI dashboard. 2. If they are correctly set up, try refreshing the web app page or clearing your browser cache to see if this resolves the issue. 3. If the problem persists, it might be a temporary glitch or a more specific issue that needs to be addressed by the VAPI support team. Since the issue is occurring on the VAPI platform, I would recommend reaching out to VAPI support for further assistance. They will be able to investigate the issue with the assistant IDs and provide a resolution. Would you like me to guide you on how to contact VAPI support?
s
how do i do that?
@Vapi
v
@SlaviSavanovic To contact VAPI support, you can typically follow these steps: 1. Visit the VAPI website and log in to your account. 2. Look for a "Support" or "Help" section on the website. This is often found in the website's footer or in the user dashboard. 3. Once you're in the Support section, you may find different options such as a support ticket system, email address, or a live chat service. 4. Submit your issue through one of the available channels. Be sure to provide details such as the assistant IDs that are not working and any error messages you're receiving. If you're unable to find the support section or if you need further assistance with the process, please let me know, and I can provide more detailed instructions or alternative methods to reach out to VAPI support.
s
I cant find anywhere where support is available... @SlaviSavanovic
@Vapi
v
@SlaviSavanovic I'm here to help you with that. If you're unable to find the support contact information on the VAPI website, you can try the following alternative methods: 1. Check any official documentation or user guides provided by VAPI for support contact information. 2. Look for a "Contact Us" page on the VAPI website, which might provide an email address or a contact form. 3. Search for VAPI's support on social media platforms, as some companies offer support through channels like Twitter or Facebook. 4. Review any emails you've received from VAPI after signing up, as they may contain support contact information. If none of these methods yield a way to contact support, I can assist you by escalating this issue internally. Would you like me to proceed with that?
s
@Vapi is that not what this channel is for?
v
@SlaviSavanovic Yes, absolutely, this channel is here to provide you with support. I apologize for any confusion. Let's try to address the issue directly through this channel. I will escalate the problem with the assistant IDs not being allowed on the demo voice call through the web app. Please give me a moment to report this issue to the technical team. Once I have done that, I will update you on the status and any further steps you might need to take. Thank you for your patience.
s
@User any idea what might be going on?
@Vapi how long does it take someone to respond?
v
@SlaviSavanovic Sweet. Have a great day!
s
cc: @Shubham Bajaj can you please take a look?
c
what is the error you are having? (not VAPi support) just tryna help.
s
c
Hmm might be a bug atm.
s
@Chowderr that's a shame. I appreciate the help my man
c
It happens for all your assistants?
s
@Chowderr nah just for the new ones I create. The first two I made work just fine. I was trying to teach someone how to use it lol and then all of a sudden when we created a new assistant for demo purposes it started throwing this up
@Chowderr it's not a consitent error message first it send transient assistants are not allowed with this key? I didn't know keys were assigned via dashboard so i was a little thrown off then it started throwing this error in the image then randomly it will just throw a failed to fetch or forbidden 403
c
Well transient assistant is not in the dashboard at all. That is a static assistant.
s
@Chowderr right - which makes me think there is a state bug that occurs at the creation of a new assistant. Not sure if i screwed something up but this all started happening when I invited a team member to my organization and they created one
@Chowderr one - as in an assistant
@Chowderr but now even when I make a new one I get the same error
c
Yea very weird. You could inspect the page and see the error that is happening.
s
@SlaviSavanovic can you please dm me.
n
Same here
before it works
but now it keeps 403 for every agent created in dashboard
s
@ngocanhnckh you issue is different you are using the wrong key.
s
because of no response closing this ticket.
g
For future people: I figured it out. I guess Vapi changed their system of API tokens and for some reason the old ones didn't have permissions. I created new API tokens and now all working as expected at least remotely.
c
i got the same message around 1pm EST on all my assistants when using talk to assistant from the vapi dashboard. can seem to get it working no matter what i do
g
c
Please also clear your cache and cookies related to VAPI domain on your browser and if you still encounter the error, create a loom screen recording with the steps to reproduce this error so our team can debug this on our side.
5 Views
PreviousNext
Powered by