Persistent 401 “Invalid Key” on /call/web despite fresh public keys
Hi Vapi Support,
I'm consistently getting a 401 Unauthorized error with the message "Invalid Key. Hot tip, you may be using the private key instead of the public key, or vice versa." when calling the /call/web endpoint.
What I've done:
• I am using the public key, not the private key.
• The assistant ID is correctly set and from the same organization as the key.
• I've tried multiple regenerated public keys — all return the same 401 error.
• I've confirmed that allowed assistants and allowed origins are blank (default, unrestricted).
• I tested from both the frontend browser dev tools and backend
At this point, I'm unsure why the request is still unauthorized.
Request:
Could someone please help me identify what’s causing the 401 and resolve it
Thanks
I'm consistently getting a 401 Unauthorized error with the message "Invalid Key. Hot tip, you may be using the private key instead of the public key, or vice versa." when calling the /call/web endpoint.
What I've done:
• I am using the public key, not the private key.
• The assistant ID is correctly set and from the same organization as the key.
• I've tried multiple regenerated public keys — all return the same 401 error.
• I've confirmed that allowed assistants and allowed origins are blank (default, unrestricted).
• I tested from both the frontend browser dev tools and backend
At this point, I'm unsure why the request is still unauthorized.
Request:
Could someone please help me identify what’s causing the 401 and resolve it
Thanks
