The VAPI Assistant Name is a privileged and important field in many cases within the API (e.g. "create tool - transfer call" requires the assistant name and not ID). VAPI Assistant names are not only not unique identifiers, but they have a 40 character limit (which is FAR too small). This makes it INCREDIBLY annoying to manage many assistants across different customers and environments. I'm requesting the following in order of priority: Increase the assistant name character limit to 256 characters Make the assistant names unique identifiers within an VAPI organization Refactor the API to leverage assistant IDs and not assistant names

I can help by suggesting an efficient workaround using assistant IDs through custom mapping logic, so you don’t have to rely on short or duplicate names. I’ve implemented similar solutions for multi-environment setups. Are you currently managing your assistants via API or dashboard? @peoplekind

Each assistant does have an ID that is separate from the name, which kind of look like

760471d3-e1c0-4021-9cc1-ef3a68666659

. We use the assistantId in our database and associate them with the org ids they belong to, which are also leveraged with the API. Do you have multiple orgs associated with your Vapi account to handle different customers? If not, separating the assistants into different orgs might help with organizing assistants. If you still would like to increase the assistant name character count, feel free to add it to the feature request list here -->

Thanks for the responses folks! Sorry for the delayed reply. I am managing this through the API and am leveraging the assistant IDs where I'm able, but if you reference the API documentation specifically for

Create Tool

you'll see that it uses the assistant name rather than the ID. The request here is not to have an ID separate from the name, it's to have consistency across the API for different IDs and to have a place to properly tag the assistants with useful attributes. I am managing these assistants for an enterprise grade application with different deployment environments and customers, and the 40 character constraint is massively limiting in my ability to distinguish between these agents.

Thank you for submitting that! Still a bit puzzled as to where you see that in the API documentation. Could you please send a link to the tool where it used assistantName instead of assistantId? I do see one reference in the handoff tool, but it's interchangeable and starts with assistantId as the main variable.