### Answer
It sounds like you're encountering a common issue when integrating custom voices from external providers like Eleven Labs into your Vapi assistant. One possible cause for this issue is related to the configuration of your 11labs account or the provision of API keys. According to a user's experience shared on a Discord forum, ensuring your 11labs API keys are correctly added to the "Provider Keys" section in the Vapi dashboard can resolve similar problems. This is mentioned in a conversation where a user faced an error and resolved it by correctly adding their 11labs ID and API keys [(1)](
) .
When using custom voices, including those from Eleven Labs, it's crucial to ensure that:
1. Your Eleven Labs account is correctly connected.
2. Your custom voice ID is correctly specified in the assistant configuration.
3. Your Eleven Labs API keys are correctly configured in the Vapi dashboard under the "Provider Keys" section.
For reference on how to specify a custom voice in your assistant's configuration, here's how you would generally do it, replacing
"your-voice-id"
with your actual custom voice ID from Eleven Labs:
json
{
"voice": {
"provider": "deepgram",
"voiceId": "your-voice-id"
}
}