---
title: "EU-based API endpoint | Guides | Maps apis | Maps platform"
description: "Keep your end users' IP addresses inside the EU."
---

> For AI agents: a documentation index is available at [/llms.txt](https://docs-beta-4y5.pages.dev/llms.txt). Markdown versions of all pages are available by appending .md to any URL.

# EU-based API endpoint

The `api.maptiler.eu` endpoint keeps your end users’ IP addresses inside the EU. It’s an alternative to [`api.maptiler.com`](https://docs-beta-4y5.pages.dev/cloud/api/) for organizations that need to make sure the IP addresses of the people using their maps and apps are never transferred outside the EU.

## What’s not covered

Some data can be processed outside the EU, no matter which endpoint you use:

-   **Your MapTiler account data.** Information about you as a MapTiler customer, such as your account and billing details, is stored on infrastructure both in and outside the EU.
-   **Request content.** To provide some services, we pass the content of a request to third-party providers that may be located outside the EU. For example, the address someone types into a [geocoding](https://docs-beta-4y5.pages.dev/guides/developer/location-services/geocoding-search/) search. This content can’t be traced back to individual end users.

For details on how we handle personal data, see the [MapTiler Privacy Policy](https://www.maptiler.com/privacy-policy/).

## Availability

The EU endpoint is available to **paid plans only**. Requests made with a free-plan API key to `api.maptiler.eu` get rejected.

Note that the EU endpoint covers the public [MapTiler API](https://docs-beta-4y5.pages.dev/cloud/api/), not the [Service API](https://docs-beta-4y5.pages.dev/cloud/admin-api/). The Service API is designed for backend-to-backend communication, such as uploading or deleting data in your account, and does not process end-user personal data.

## How to use

Replace `api.maptiler.com` with `api.maptiler.eu` in your request URLs. The paths, parameters, and [API keys](https://docs-beta-4y5.pages.dev/guides/credentials/api-key/) remain identical on both endpoints.

Example:

```js
https://api.maptiler.eu/maps/streets-v4/?key=YOUR_MAPTILER_API_KEY#1.0/0.00000/0.00000
```

### With MapTiler SDK JS

[MapTiler SDK JS](https://docs-beta-4y5.pages.dev/sdk-js/) supports the EU endpoint from version **4.2.0**. To route all requests through the EU endpoint, set `config.useEuEndpoints` to `true`.

Example:

```js
maptilersdk.config.apiKey = 'YOUR_MAPTILER_API_KEY';
maptilersdk.config.useEuEndpoints = true;

const map = new maptilersdk.Map({
  container: 'map',
  style: maptilersdk.MapStyle.STREETS,
});
```

## Geolocation accuracy

With the EU endpoint, [IP geolocation](https://docs-beta-4y5.pages.dev/guides/developer/location-services/ip-geolocation/) is less accurate for end users located outside Europe. This can affect the prioritization of [geocoding](https://docs-beta-4y5.pages.dev/guides/developer/location-services/geocoding-search/) search results. If your application serves a global audience and needs maximum geolocation accuracy, we recommend that you continue using `api.maptiler.com`.