Endpoint Options
Choosing EU
Use the default endpoint for automatic geo-routing. Select EU only when you need to pin traffic to Europe.How to Set Your Region
You can select the direct EU endpoint with an API-key prefix or an explicit region. You can also bypass region resolution by supplying an API URL directly.Option 1: Prefix Your API Key
Prependeu- to your API key. The prefix is stripped automatically before
authentication — the server never sees it.
This is the simplest approach, especially when your API key comes from an environment variable:
Option 2: Set the Region in Code
All SDKs accept an explicit EU region parameter:- Python
- JavaScript
- Java
- cURL
Priority
When multiple EU endpoint hints are present, the SDK resolves them in this order:- Explicit API URL —
api_urlin Python,apiUrlin JavaScript, orapiUrlin Java region— explicit EU region parameter- API key prefix —
eu- - Default — canonical geo-routed API (
api.kugelaudio.com)
WebSocket Connections
EU endpoint selection applies to both REST and WebSocket endpoints. The SDK automatically uses the correct host for WebSocket connections:FAQ
Do I need to change anything if I use the default endpoint?
Do I need to change anything if I use the default endpoint?
If you want automatic geo-routing, no. If you need to pin traffic to Europe, set
region="eu" or use the eu- API key prefix.Are voices and models the same across regions?
Are voices and models the same across regions?
Query
/v1/models and /v1/voices on the endpoint you plan to use to
confirm its current catalog and your custom-voice availability.Can I switch regions without getting a new API key?
Can I switch regions without getting a new API key?
Yes. Your API key works with the default and EU endpoints — just add or remove the
eu- prefix or region="eu" parameter. No need to regenerate keys.