Please fully refresh the Convai dashboard, open the new Playground, and reopen the voice selector for character e7b69296-6edb-11f1-8f7a-42010a7be02e. Ginevra (75MqelvgFq5upx0r44WK) should now appear among your ElevenLabs workspace voices.
If it is still missing after refreshing, please let us know the approximate time of the test so we can correlate it with the request logs.
You can edit the existing key through More Actions (…) → Edit; you do not need to generate another key solely to add User access.
Once updated, please use the new Playground from the Convai dashboard to select the voice. The legacy Playground does not load ElevenLabs workspace voices through the new voice selector. After opening the new Playground, refresh the page and reopen the voice list.
Hi CH, we’ve deployed a fix for ElevenLabs voice discovery. Please try selecting your voice again in the new Playground and let us know if it now appears.
However, the main cause of this issue appears to be a recent change on ElevenLabs’ side related to API keys, which was made without prior notice. This is not a Convai-side issue.
We have also seen other users publicly reporting similar ElevenLabs API key issues, for example here: Reddit
Our teammates are updating the integration to better handle these new changes from ElevenLabs. We understand the frustration, and we are working to resolve this as soon as possible.
It’s been working for me since yesterday, thanks. (The voice still doesn’t sound as good as it does in ElevenLabs Studio or via non-streaming direct ElevenLabs API call, but I guess that’s a separate issue)
We reproduced the issue and found the exact cause. The credential currently connected to your Convai account is an ElevenLabs API key ID, not the complete API key secret. ElevenLabs is rejecting it with:
API key ID used as API key. Only valid API keys can be used. API keys start with sk_.
Please create or rotate the key in ElevenLabs and copy the complete sk_ value shown at creation time, rather than the identifier displayed in the API key list. It needs User Access, Voices Read, and Text to Speech Access.
Then remove the existing ElevenLabs integration in Convai and add it again with that sk_ value. Please let us know once this single update is complete; we will verify it server-side so you do not need to keep repeating the process.
We are also updating Convai to reject key IDs immediately and show this specific error instead of accepting the integration and failing later.
Hi Matthew, thanks for confirming. It appears the new key did not replace the existing integration record.
Please remove the ElevenLabs integration from Convai completely, then add it again using the full sk_ key you created. We have now added connection-time validation, so an invalid key or missing permissions should be rejected immediately with a specific error instead of saving and failing later.
If the integration saves successfully, please refresh the new Playground and select your voice again. Let us know once completed and we’ll verify it from our side.
It says this now! API key ID used as API key - only valid API keys can be used. API keys start with ‘sk_’ and are shown when the key is created or rotated.
I Know it’s not true. I need this working yesterday! I’m beyond frustrated. Please fix this.
Hi Matthew, thank you for your patience while we fix this.
We’ve deployed and validated the fix in production. Please remove the existing ElevenLabs integration, add it again using the full sk_ API key with User Read, Voices Read, and Text to Speech permissions, then use the new Playground to select one of your test voices. The integration will now validate the key and permissions when it is added, so any remaining problem should be shown immediately with a specific error.