Skip to main content
By default, SDKs use the canonical geo-routed endpoint. Existing API keys and SDK code continue to work without changes. Select the direct EU endpoint only when you need to pin traffic to Europe.

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

Prepend eu- 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:
No code changes needed — the SDK detects the prefix and uses the EU endpoint.

Option 2: Set the Region in Code

All SDKs accept an explicit EU region parameter:

Priority

When multiple EU endpoint hints are present, the SDK resolves them in this order:
  1. Explicit API URLapi_url in Python, apiUrl in JavaScript, or apiUrl in Java
  2. region — explicit EU region parameter
  3. API key prefixeu-
  4. 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

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.
Query /v1/models and /v1/voices on the endpoint you plan to use to confirm its current catalog and your custom-voice availability.
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.