Feature Requests

soniox.com does a really good job at european languages. I can't find any other STT that works so fine for Romanian.

While Vapi currently supports HIPAA compliant use cases, today it only covers the /call endpoint. It would be very helpful to also support the other communication pathways, specifically /chat.

I need to be able to use the display name for VAPI assistants to tag an assistant with various attributes that would be useful, as well as have more descriptive names for my assistant. Specifically, I have different VAPI assistants for different environments under the same organization (e.g. "dev0", "dev1", ...) and different VAPI assistants for different customers. The name "production - Arizona Cardiovascular Institute - Inbound - Prescription Refill Request" is completely out of bounds of the 40 character limit, but is very useful for both readability purposes and for specifying the assistant name at a granular level for things like configuring tools. I think that 256 is a standard character count that would give enough flexibility here. Also, there are places in the API (e.g. Create Tool where you specify assistant destinations by assistantName rather than assistantId) that privilege the assistant name. I think that you should theoretically be able to use either.

BUG: When you create a widget from an assistant and set the customizable features (appearance, layout, text & labels etc.) it works and is embedabble. When you return to make a change at a later date and click 'customize' all the settings reset to the default and you loose everything you designed.

Hello, 4.5 Sonnet was released yesterday. Please add it, thank you!

can we please get grok-4-fast-non-reasoning. decent speed, incredibly cheap, very smart. please add in support for this

After being directed to landing page once URL is entered. It seems that screen or page goes black once I attempt to sign in or sign up. No option to escape or continue without going back to previous page. Im not able to sign up or sign in. Can I understand how to get around this.

I need to be able to use the display name for VAPI assistants to tag an assistant with various attributes that would be useful, as well as have more descriptive names for my assistant. Specifically, I have different VAPI assistants for different environments under the same organization (e.g. "dev0", "dev1", ...) and different VAPI assistants for different customers. The name "production - Arizona Cardiovascular Institute - Inbound - Prescription Refill Request" is completely out of bounds of the 40 character limit, but is very useful for both readability purposes and for specifying the assistant name at a granular level for things like configuring tools. I think that 256 is a standard character count that would give enough flexibility here. Also, there are places in the API (e.g. Create Tool where you specify assistant destinations by assistantName rather than assistantId) that privilege the assistant name. I think that you should theoretically be able to use either.

https://docs.vapi.ai/api-reference/calls/get returns promptTokens and completionTokens but is missing cached_input tokens. To properly model our costs, we need to know the breakdown.