Cloned voice from elevenlabs unable to sync with v...
# support
c
I am unable to sync my new elevenlab voice to vapi. It is not accepting the api key for elevenlabs. I have tried everything and need some assistance please.
k
To help track down this issue, could you share one or two: - The call ID - When exactly this happened (the timestamp) - What response you expected to get - What response you actually got instead This would really help us figure out what went wrong!
c
@Kings_big💫 It's not a matter of a specific call. It's a matter of connecting a voice that I recorded from elevenlabs to vapi. Whenever I try to copy my clone ID and paste it into vapi, I receive the following error message: "Error updating assistant" "Couldn't find 11labs voice. If your using your credentials, check the voice exists in your 11labs account. If not, check the voice exists in the provided list. Hot tip, remove your credential if you're trying to use a vapi provided voice"
Hi @Kings_big💫 I have two support tickets up right now. This one about the cloned voice is priority number one over the other. Can you please assist with this clone voice not syncing up with Vapi?
k
This happens because you’re using a free-tier 11Labs API key, switching to a paid plan and generating a new unrestricted API key usually fixes this. If you’re already on a paid plan, regenerate the key and ensure it’s correctly pasted in Vapi → Integrations tab..
c
@Kings_big💫 I am on the creator plan and have tried generating 3 new keys and correctly pasted them into Vapi Integrations tab. The 11labs api key starts with sk. I paste this key into vapi integrations and it pulls up an error code that says: "Error in saving credentials. Couldn't validate 11labs credential. Error: Request failed with status code 401"
@Kings_big💫 I'm getting a persistent 401 error when adding my ElevenLabs API key to Vapi, even though I've done the following: I'm on the ElevenLabs Creator Plan Generated a brand new API key with full scopes: Text to Speech, Voices (read/write), Projects, Models (Full Access) Confirmed the key works via Postman/Hoppscotch (/v1/voices returns 200 OK) Cleared Vapi cache, used incognito mode, and created a fresh assistant Pasted the key into the correct field in Vapi → Integrations → Provider Key API Key ends in: ...85ef ElevenLabs Org ID (if needed): 00280610-8f20-4528-9ddb-f89c5b6a163b Can you check if something’s stuck on your backend?
k
Please can you share a loom video
k
Looking into it
c
Thank you
j
I have the same problem and Elevenlabs has confirmed that the API Key I'm using is valid
c
@Kings_big💫 Were you able to figure out the issue?
@Kings_big💫 Every time I generate a new elevenlabs api key it starts with "sk_" Is this the correct formatting for Vapi?
k
You need to create a new 11Labs API key that grants all scopes and access. Only then can you use it with VAPI. Even if we configure for scope-based access, we need to perform a few operations using the 11Labs API, and the current scoping system conflicts with this. Therefore, you must grant the API key full access control and scopes. Once you have done so, share the API key with us.
c
That was it. Thank you!
4 Views