Private And Public Key Issues since menu moved to ...
# supportg
Gilang
05/17/2025, 3:00 AMHi, We to create another organization to testing some features. We realize that API key menu moved. So there must be some changed.
When we tried to create new assistant we got this error when everything is correct. I think this affecting new organization only:
Body: {
"message": "Invalid Key. Hot tip, you may be using the private key instead of the public key, or vice versa.",
"error": "Unauthorized",
"statusCode": 401
}
Gilang
05/17/2025, 3:21 AM@ivy @Shubham Bajaj @User
Gilang
05/17/2025, 4:54 AMIts working now. Thanks
y
Yash Tyagi
05/18/2025, 1:50 PMwhat's the fix?
g
Gilang
05/19/2025, 2:39 AMBefore we use new org but always failed to fill credit. And then create new organization succeed to filled the credit but failed in API key.
I dont know why suddenly the API key Work
p
Praveen
05/19/2025, 4:01 PMHey Gilang, can Hi there, it sounds like you might be using a private key when a public key is needed, or vice versa. Double-check which key you're using for the action you're trying to perform. Use the Provider Keys section in your Vapi dashboard to verify. If this is specifically affecting your new organization, ensure you've set the right permissions for the keys there. Let me know if you continue having trouble, and I'll be here to help.