---
title: "EU-based API endpoint | Guides | Maps apis | Maps platform"
description: "How to use the api.maptiler.eu endpoint to keep end-user requests within EU infrastructure."
---

> For AI agents: a documentation index is available at [/llms.txt](https://docs-qmgv.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 routes every API request exclusively through EU-based infrastructure. It serves as an alternative to [`api.maptiler.com`](https://docs-qmgv.pages.dev/cloud/api/) for organizations that need a guarantee that end-user personal data (mainly IP addresses) is never processed by non-EU entities.

For general information on data processing practices, see [how we handle personal data](https://docs-qmgv.pages.dev/guides/maps-apis/maps-platform/personal-data-in-maptiler-cloud/).

## Availability

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

## How to use

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

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

Note

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