Eleven Labs Integration Refuses Valid API Key ("Invalid API Key")

[jdkang]

The problem

The official Eleven Labs HA integration won't accept my API keys. Tried doing some google/forum searching, but didn't find anything recent (past few months).

Problem persists through Core and even OS reboots.

I have generated multiple keys and tested them in python, e.g.

#! /bin/python3
from elevenlabs import save, play
from elevenlabs.client import ElevenLabs

api_key = "sk_xxxxxxxxxxxxxxxxxxxxxxxxxxxx"

client = ElevenLabs(api_key=api_key)
audio = client.text_to_speech.convert(
    text="your api key works",
    voice_id="JBFqnCBsd6RMkjVDRZzb",
    model_id="eleven_multilingual_v2",
    output_format="mp3_44100_128",
)

save(audio, "output.mp3")

This appears to be the URL it's posting the key to:
http://homeassistant.local:8123/api/config/config_entries/flow/01JYSBKXVR7JCGJ6GK0511R0AV

with a PAYLOAD like this:

{"api_key":"sk_xxxxxxxxxx"}

which does return a 200 OK (i.e. ostensibly not a client/server issue)

HAOS info

Installation method Home Assistant OS
Core 2025.6.3
Supervisor 2025.06.2
Operating System 15.2
Frontend 20250531.4

What version of Home Assistant Core has the issue?

core-2025.6.3

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

ElevenLabs

Link to integration documentation on our website

https://www.home-assistant.io/integrations/elevenlabs/

Diagnostics information

No response

Example YAML snippet

Anything in the logs that might be useful for us?

Additional information

No response

[home-assistant]

Hey there @sorgfresser, mind taking a look at this issue as it has been labeled with an integration (elevenlabs) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of elevenlabs can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign elevenlabs Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

elevenlabs documentation
elevenlabs source
_{^{(message by IssueLinks)}}

[github-actions]

🔍 Potential duplicate detection

I've analyzed similar issues and found the following potential duplicates:

• #147667: Elevenlabs Invalid API Key

What to do next:

1. Please review these issues to see if they match your issue
2. If you find an existing issue that covers your problem:
   • Consider closing this issue
   • Add your findings or 👍 on the existing issue instead
3. If your issue is different or adds new aspects, please clarify how it differs

This helps keep our issues organized and ensures similar issues are consolidated for better visibility.

This message was generated automatically by our duplicate detection system.

[sorgfresser]

Can't reproduce sadly, but you're not the first person to report this, so I'm sure there's something wrong. Works for me though. Would you mind trying this branch? #147224

I'm more than happy to guide you through the process.

[sorgfresser]

Okay, can reproduce if I use one of the new API keys. This is related to ElevenLabs changing their auth. #147224 should fix it.

[sorgfresser]

Okay, this is most likely related to permission issues within your elevenlabs API key configuration. Please try adjusting the permissions for your API key. I assume elevenlabs changed how they treat these keys.

[old-square-eyes]

Not OP but from another ticket merged. Good find. What permissions are recommended? There are a lot.

(I enabled everything and it works but it would be good to doc which ones are actually needed for the integration)

[jdkang]

Not OP but from another ticket merged. Good find. What permissions are recommended? There are a lot.

(I enabled everything and it works but it would be good to doc which ones are actually needed for the integration)

@sorgfresser so I got it to work with the following permissions

• text to speech
• sound effects
• voices (ro)
• models (ro)

Perhaps the UI can be updated to to reflect the minimum permissions required since everything is no access by default and intuitively a user might assume that text-to-speech is enough.

[issue-triage-workflows]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.