Skip to main content
By default, SDKs use the canonical geo-routed endpoint. Select the direct EU endpoint only when you need to pin traffic to Europe.
Need your data to stay on your own infrastructure? See On-Premise Deployment (Enterprise).

Endpoint Options

How to Set Your Region

The SDKs select the direct EU endpoint from an API-key prefix or an explicit region. You can also bypass region resolution by supplying an API URL directly. Without an SDK, call the EU host yourself.

Option 1: Prefix Your API Key (SDKs only)

Prepend eu- to your API key. The SDK strips the prefix before sending the key and routes the request to the EU endpoint:
No code changes needed. The prefix is an SDK feature: the API itself does not recognize it, so a raw HTTP or WebSocket request with a prefixed key fails with 401 Invalid API key.

Option 2: Set the Region in Code

All SDKs accept an explicit EU region parameter:
With the async client:

Priority

When multiple EU endpoint hints are present, the SDK resolves them in this order:
  1. Explicit API URL: api_url in Python, apiUrl in JavaScript, or apiUrl in Java
  2. region: explicit EU region parameter
  3. API key prefix: eu-
  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. Raw WebSocket clients connect to the EU host with the unprefixed key:

FAQ

If you want automatic geo-routing, no. If you need to pin traffic to Europe, set region="eu" or the eu- key prefix in an SDK, or call api.eu.kugelaudio.com directly.
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. In an SDK, add or remove the eu- prefix or the region="eu" parameter; without an SDK, change the host. No need to regenerate keys.

Next steps

Authentication

Create and use API keys

On-Premise Deployment

Run KugelAudio on your own infrastructure
Last modified on September 22, 2026