If your compliance team has been asking whether your users’ IP addresses ever leave the EU, you can now give them a clear answer: once you switch to the EU endpoint, they don’t.
Whenever a visitor loads a map on your site, their browser fetches the map from your provider and sends their IP address along with the request.
Under GDPR, that IP address counts as personal data. Our default endpoint (api.maptiler.com) runs on a global network, so each request is handled by whichever server is closest to the visitor, and that server can be anywhere in the world.
For most websites and mobile apps, that’s perfectly acceptable. But if you build for European banks, public sector clients, or healthcare platforms, “acceptable” often isn’t enough to pass procurement and vendor reviews, especially with the ongoing turbulence around EU–US data pacts.
How to migrate to the EU map endpoint
Nothing changes in your code beyond the host. Your existing paths, parameters, and API keys work as-is.
Direct HTTP / REST API calls
Swap the host in your request URLs:
Before
https://api.maptiler.com/maps/streets-v4/...After
https://api.maptiler.eu/maps/streets-v4/...MapTiler SDK JS configuration
The SDK builds its request URLs for you, so instead of editing URLs, turn on one setting when your app starts:
maptilersdk.config.apiKey = 'YOUR_MAPTILER_API_KEY_HERE';
maptilersdk.config.useEuEndpoints = true;
const map = new maptilersdk.Map({
container: 'map',
style: maptilersdk.MapStyle.STREETS,
});Technical scope and data residency considerations
A few technical details worth knowing before switching:
- What routes through the EU: End-user-facing requests (vector tiles, raster tiles, geocoding/search, and terrain/elevation). These are the calls originating from user devices that carry their IP addresses, which are processed only on EU infrastructure.
- What doesn’t: Server-side management APIs (uploading datasets, editing tilesets, fetching account analytics) are still processed to deliver the service, but without the user’s IP address attached, so it can’t be traced back to them.
- The trade-off on global geocoding: Our search uses a visitor’s rough location to show nearby results first. With the EU endpoint, that works a bit less well for visitors outside Europe, so someone in Chicago searching for “Springfield” might not see the Illinois one at the top. If most of your users are outside Europe and rely on search, api.maptiler.com is the better fit.
- Availability: Available today on all paid plans.
Get started
Already on a paid plan? Follow the setup guide and switch in a few minutes.
On the free plan? Compare paid plans and sign up to get the EU endpoint option.




