> This page is for Data API, version v2 (default).
> For other versions, use one of these documentation indexes:
> - v2 (default): https://developers.webflow.com/data/v2.0.0/llms.txt
> - v2 Beta: https://developers.webflow.com/data/v2.0.0-beta/llms.txt
> - v1: https://developers.webflow.com/data/v1.0.0/llms.txt

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://developers.webflow.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://developers.webflow.com/_mcp/server.

# EU Hosting

> Use the Data API, OAuth, the SDKs, the MCP server, and the Webflow CLI with Webflow workspaces hosted in the EU.

Enterprise customers can host their Webflow workspaces in the EU. These workspaces run in a separate Webflow region, with their own accounts, sites, and data.

The Data API works the same way in both regions. The endpoints, request bodies, and responses don't change. To work with an EU workspace, use the EU host names and credentials that the EU region issues.

To build an app that supports both regions, follow [Working with EU Hosting](/data/docs/working-with-eu-hosting).

> **Note**
>
> EU Hosting is available on Enterprise plans. To set up an EU workspace, contact your Webflow account team.

## Host names

| Service                             | US                           | EU                              |
| :---------------------------------- | :--------------------------- | :------------------------------ |
| Webflow app and OAuth authorization | `webflow.com`                | `eu.webflow.com`                |
| Data API and OAuth token            | `api.webflow.com`            | `api.eu.webflow.com`            |
| MCP server                          | `mcp.webflow.com`            | `mcp.eu.webflow.com`            |
| Staging domains                     | `*.webflow.io`               | `*.eu.webflow.io`               |
| Asset CDN                           | `cdn.prod.website-files.com` | `cdn.prod.eu.website-files.com` |

The paths are the same in both regions. For example, the EU Data API base URL is `https://api.eu.webflow.com/v2`, and the EU MCP server URL is `https://mcp.eu.webflow.com/mcp`.

## Accounts and tokens

Each region has its own accounts, workspaces, and sites. Credentials from one region don't work in the other:

* Create [site tokens](/data/reference/site-token) and [workspace tokens](/data/reference/workspace-token) for EU sites on `eu.webflow.com`.
* Send EU tokens to `api.eu.webflow.com`. The US API rejects EU tokens, and the EU API rejects US tokens.

## OAuth apps

An app that you register on `webflow.com` can't authorize users in EU workspaces. To support EU workspaces, also [register your app](/data/docs/getting-started-apps) from a workspace on `eu.webflow.com`. The EU registration gives your app a separate client ID and client secret.

Then follow the usual [OAuth flow](/data/reference/oauth-app) with the EU hosts:

1. Send the user to `https://eu.webflow.com/oauth/authorize` with your EU client ID.
2. Exchange the authorization code at `https://api.eu.webflow.com/oauth/access_token` with your EU client ID and client secret.
3. Call the Data API at `https://api.eu.webflow.com/v2` with the access token.

Store the region with each access token, so that later requests go to the right API.

> **Tip**
>
> If your app serves both regions, ask users for their region before you start the OAuth flow. For example, show a separate option to connect a Webflow EU workspace.

## SDKs

The [JavaScript and Python SDKs](/data/reference/sdks) call the US API by default. To call the EU API, set the EU base URL when you create the client:

**`JavaScript`**

```javascript title="JavaScript"
import { WebflowClient } from "webflow-api";

const webflow = new WebflowClient({
  accessToken: process.env.WEBFLOW_EU_TOKEN,
  baseUrl: "https://api.eu.webflow.com/v2",
});

const sites = await webflow.sites.list();
```

**`Python`**

```python title="Python"
import os

from webflow import Webflow, WebflowEnvironment

client = Webflow(
    access_token=os.environ["WEBFLOW_EU_TOKEN"],
    environment=WebflowEnvironment(
        base="https://api.eu.webflow.com/v2",
        data_api="https://api.eu.webflow.com/v2",
        content_delivery_api="https://api.eu.webflow.com/v2",
    ),
)

sites = client.sites.list()
```

> **The SDK OAuth helpers use the US hosts**
>
> The OAuth helpers in the SDKs always use the US hosts. These are `WebflowClient.authorizeURL` and `WebflowClient.getAccessToken` in JavaScript, and `authorize_url` and `get_access_token` in Python. For EU workspaces, build the authorization URL and request the access token yourself.

This example builds the EU authorization URL and exchanges the code for an access token:

**`EU OAuth flow`**

```javascript title="EU OAuth flow"
// Send the user to the EU authorization page
const params = new URLSearchParams({
  response_type: "code",
  client_id: process.env.WEBFLOW_EU_CLIENT_ID,
  redirect_uri: process.env.WEBFLOW_EU_REDIRECT_URI,
  scope: "sites:read cms:read",
  state,
});
res.redirect(`https://eu.webflow.com/oauth/authorize?${params}`);

// In your redirect handler, exchange the code for an access token
const response = await fetch("https://api.eu.webflow.com/oauth/access_token", {
  method: "POST",
  headers: { "Content-Type": "application/json" },
  body: JSON.stringify({
    client_id: process.env.WEBFLOW_EU_CLIENT_ID,
    client_secret: process.env.WEBFLOW_EU_CLIENT_SECRET,
    code,
    grant_type: "authorization_code",
    redirect_uri: process.env.WEBFLOW_EU_REDIRECT_URI,
  }),
});
const { access_token } = await response.json();
```

## MCP server

To use the [Webflow MCP server](/mcp/reference/getting-started) with an EU workspace, connect your AI client to `https://mcp.eu.webflow.com/mcp` instead of `https://mcp.webflow.com/mcp`. When your client asks you to authorize, sign in with your EU account.

The EU server has the same tools as the US server, except `ask_webflow_ai`. Analyze, Optimize, and AEO (answer engine optimization) aren't available in the EU region. Their tools (`data_analyze_tool`, `data_optimize_tool`, and `data_aeo_tool`) appear in your client's tool list, but return an error or no data for EU workspaces.

### Designer tools

The [Designer tools](/mcp/tools/designer-tools) work on EU sites. They need the MCP app, which installs automatically when you authorize the EU server. In the EU region, the app's name is **Webflow MCP**, not "Webflow MCP Bridge App" as in the US region.

To connect the app to a Designer session:

1. Open your site in the Webflow Designer on `eu.webflow.com`.
2. Press the `E` key to open the Apps panel.
3. Launch the **Webflow MCP** app.
4. Wait for the app to connect to the MCP server.

Keep the app open while you use the Designer tools. You can minimize it after it connects. For more about the app, see [Webflow MCP Bridge App](/mcp/reference/how-it-works#webflow-mcp-bridge-app).

## Webflow CLI

The [Webflow CLI](/cli/authentication) targets the US region by default. To target the EU region, use the `--region eu` flag, the `WEBFLOW_REGION` environment variable, or the `region` field in `webflow.json`:

```bash
webflow --region eu auth login
webflow --region eu sites list
```

For the full setup, see [Production EU authentication](/cli/authentication#production-eu-authentication) and [region configuration](/cli/configuration#region).

## Webflow Cloud

To deploy a Webflow Cloud app for an EU site, set the CLI to the EU region before you deploy. Webflow creates [SQLite](/webflow-cloud/storing-data/sqlite) databases and [Object Storage](/webflow-cloud/storing-data/object-storage) buckets for EU apps in the EU jurisdiction.

The [Key Value Store](/webflow-cloud/storing-data/key-value-store) is an exception. Webflow stores its data in the EU, but the data can be cached and read outside the EU. Don't use it for data that must stay in the EU.

## Not available in the EU region

These features aren't available for EU workspaces:

* Apps from the Webflow Marketplace, including third-party Designer Extensions
* Analyze, Optimize, and AEO
* The `ask_webflow_ai` tool on the MCP server