re-added new public and private keys. did hard refresh with all website storage clean up. Still seeing same message. Please advice. Thank you. https://cdn.discordapp.com/attachments/1464701218407583993/1464701218868695040/image.png?ex=69766ccf&is=69751b4f&hm=187e9314893b88395e27d0ebef7f45fb3a4af4a7e6488e4a6d8d3d1a393e8c00&

Hi there, Thank you for your message. Our team is currently out of the office. We operate Monday through Friday, from 9:00 AM to 8:00 PM Pacific Standard Time (PST). We’ll get back to you as soon as possible during our normal business hours. If your message is urgent, please mark it accordingly or include “URGENT” in the subject line, and we’ll do our best to respond promptly. Warm regards, Vapi Customer Support Team

Since you've already tried key regeneration and a hard refresh, the best next step is to report this as a Dashboard & UI issue using the recommended format. Please gather the following details: - Browser & version - Operating system - Steps to reproduce - Console errors (F12) - Screenshot of the error Then, submit this information to Vapi support as shown below:

Issue: "Talk to assistant" shows "Invalid Key" error after key reset and refresh.
Browser: [Your browser/version]
OS: [Your OS]
Steps: [Step-by-step actions]
Console errors: [Paste any errors]
Screenshot: [Attach image]

This will help the support team resolve your issue efficiently according to the [issue reporting guide](https://docs.vapi.ai/issue-reporting). Source: - [How to Report Issues Effectively](https://docs.vapi.ai/issue-reporting)

Hi Andrel, Even after deleting the default key, the frontend may continue sending the old (now deleted) key in the Authorization header, which results in a 401 Unauthorized error. Client‑side fix: 1. Go to Vapi Dashboard → API Keys → Public API Keys 2. Create a new Public API key • You can reuse the same name as before • Leave all other options blank 3. Click Create Public Token 4. Perform a hard refresh of the dashboard (Ctrl + Shift + R) 5. Go back to your assistant and click “Talk to assistant” This forces the dashboard to pick up the new public key instead of the cached one. Please try this and let us know if it resolves the issue.

hey Shaunak, thank you for your response. I had brand new assistant and brand new key. I am not sure those steps can be applied. 🙁

Could you please share a screenshot of the API Keys section (censor the keys.)