Thanks — I hear that you’re trying to use an ElevenLabs residency API key and need to assign a custom API URL for the ElevenLabs TTS plugin because the default endpoint won’t work for your residency endpoint. I can help — quick question first: Which SDK are you using with LiveKit’s ElevenLabs TTS plugin: Python or Node.js? If you’re using Python • The Python

ElevenLabsTTS

plugin accepts an optional

base_url

parameter so you can point requests to a residency endpoint. Example:

from livekit.plugins import elevenlabs

tts = elevenlabs.TTS(
    voice_id="ODq5zmih8GrVes37Dizd",
    model="eleven_multilingual_v2",
    base_url="<https://api.region.elevenlabs.io/v1>"  # replace with your residency endpoint
)

• Make sure you’re on a recent

livekit-plugins-elevenlabs

version that includes

base_url

. If you’re using Node.js • The Node.js plugin does not currently expose

base_url

in the constructor. Your options are: ◦ Extend or patch the plugin code to add a

base_url

option and use it when building requests. ◦ Put a small proxy/middleware in front of the plugin that forwards requests to your residency endpoint. ◦ Confirm if the ElevenLabs residency setup can be used just by the API key (some residency setups route automatically); if so you might not need to change the URL. • If you tell me which option you prefer, I can show a code example for patching the plugin or for creating a lightweight proxy. Next steps I can help with • If Python: help update your code and check the plugin version. • If Node.js: provide a patch example or a simple Express proxy you can run locally. • If you have your residency endpoint URL and any error messages you’re seeing, paste them and I’ll give exact changes to make. Which SDK are you using, and can you share the residency URL or the error text you get when trying to set the API URL? Sources: ElevenLabs TTS | LiveKit Documentation