Skip to content

EU Endpoints

Our commitment to privacy begins in our earliest days as a company, and we take extreme care to run all of our services with a focus on ensuring the privacy of our customers and users. While we are confident that our privacy practices and procedures satisfy GDPR requirements by default, we recognize that some customers prefer to guarantee that user requests and personally identifiable information (PII) remain within the European Union.

To accommodate this preference, we publish EU-only endpoints. These endpoints ensure users exclusively connect to EU-based servers. Our systems scrub PII at the network's edge; consequently, any requests processed by our internal services in other regions are managed in a completely private manner.

Using the EU Endpoints


By utilizing EU endpoints, you will establish connections exclusively with two of our servers strategically positioned in the European Union: Frankfurt, Germany and Paris, France.

To use the EU endpoints, substitute the endpoints in our documentation as shown below.

Map Endpoints

For map tiles and services, replace:
Example: Using EU Endpoints for MapLibre & Alidade Smooth
<!DOCTYPE html>
        <meta charset="utf-8" />
        <title>Vector Map Demo</title>
        <meta name="viewport" content="initial-scale=1,maximum-scale=1,user-scalable=no" />
        <script type="text/javascript" src="//"></script>
        <link href="//" rel="stylesheet" />
        <style type="text/css">
            body {
              margin: 0;
              padding: 0;

            #map {
              position: absolute;
              top: 0;
              bottom: 0;
              width: 100%;
        <div id="map"></div>
        <script type="text/javascript">
         var map = new maplibregl.Map({
           container: 'map',
           style: '',  // (1)!
           center: [12, 53],  // Initial focus coordinate
           zoom: 4

         // MapLibre GL JS does not handle RTL text by default, so we recommend adding this dependency to fully support RTL rendering.

         // Add zoom and rotation controls to the map.
         map.addControl(new maplibregl.NavigationControl());
  1. This line is the key change; note the tiles-eu host.


Known bug: currently, the Alidade Satellite theme does not fully respect the EU server selection, and will continue loading the satellite tiles via the normal domain. This will be fixed in an upcoming release.

API Endpoints

For routing, geocoding, time zone, and other services, replace:

Example Code

Here are some code examples of using the EU endpoints with our official SDKs and cURL.

import { GeospatialApi, Configuration{{ extra_js_imports }} } from '@stadiamaps/api';

// If you are writing for a backend application or can't use domain-based auth,
// then you'll need to add your API key like so:
// const config = new Configuration({ basePath: "", apiKey: "YOUR-API-KEY" });
const config = new Configuration({ basePath: "" });
const api = new GeospatialApi(config);

const res = await api.tzLookup({ lat: 40.71278, lng: -74.00611 });
import os
import stadiamaps
from import ApiException

configuration = stadiamaps.Configuration(host="")

# Configure API key authentication (ex: via environment variable).
configuration.api_key['ApiKeyAuth'] = os.environ["API_KEY"]

with stadiamaps.ApiClient(configuration) as api_client:
    # Create an instance of the API class
    api_instance = stadiamaps.GeospatialApi(api_client)

        res = api_instance.tz_lookup(40.71278, -74.00611)
    except ApiException as e:
        # Add your error handling here
        print("Exception when calling the Stadia Maps API: %s\n" % e)
// Imports (at the top of your source file; we've used some wildcard imports for simplicity)
import com.stadiamaps.api.apis.*
import com.stadiamaps.api.auth.ApiKeyAuth
import com.stadiamaps.api.infrastructure.*
import com.stadiamaps.api.models.*

// Set your API key (from an environment variable in this case)
val apiKey = System.getenv("STADIA_API_KEY") ?: throw RuntimeException("API Key not set")

val client = ApiClient(baseUrl = "")
client.addAuthorization("ApiKeyAuth", ApiKeyAuth("query", "api_key", apiKey))

// Configure a service for the group of APIs we want to talk to
val service = client.createService(
val res = service.tzLookup(37.56, 126.99).execute()

if (res.isSuccessful) {
    println("Found result: ${res.body()}")
} else {
    println("Request failed with error code ${res.code()}")
import StadiaMaps

// This setup code can go anywhere before you actually make an API call (typically in your app init)
func setupStadiaMapsAPI() {
    // Set your API key
    StadiaMapsAPI.customHeaders = ["Authorization": "Stadia-Auth YOUR-API-KEY"]
    // Configure the client to use our EU endpoint
    StadiaMapsAPI.basePath = ""

// This function demonstrates how to call the Stadia Maps API.
// If you have not yet adopted async/await in your Swift codebase, you can use the Task API
// to call async functions in a non-async context:
func myFunction() async throws {
    let res = try await GeospatialAPI.tzLookup(lat: 40.71278, lng: -74.00611)

    // Do something with the response...
curl ""