New: EU Hosting docs for developers
Enterprise customers can now host their Webflow workspaces in the EU. 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 the credentials that the EU region issues.
Two new pages explain how:
- EU Hosting lists the EU host names and covers tokens, OAuth apps, the SDKs, the MCP server, the Webflow CLI, and Webflow Cloud.
- Working with EU Hosting shows how to build an app that supports both regions.
EU host names
What to know
- Tokens work only in their own region. Send EU tokens to
api.eu.webflow.com. The US API rejects EU tokens, and the EU API rejects US tokens. - OAuth apps need an EU registration. Register your app from a workspace on
eu.webflow.comto get a separate client ID and client secret. Then run the OAuth flow with the EU hosts. - SDKs: set the base URL to
https://api.eu.webflow.com/v2when you create the client. The SDK OAuth helpers always use the US hosts, so build the EU authorization URL and token request yourself. - MCP server: connect your AI client to
https://mcp.eu.webflow.com/mcp. The EU server has the same tools as the US server, exceptask_webflow_ai. In the EU region, the Designer tools use the Webflow MCP app. - Webflow CLI: add
--region eu, or setWEBFLOW_REGIONor theregionfield inwebflow.json. See Production EU authentication. - Webflow Cloud: SQLite databases and Object Storage buckets for EU apps are in the EU jurisdiction. For the Key Value Store, Webflow stores its data in the EU, but the data can be cached and read outside the EU.
Not available in the EU region
- Apps from the Webflow Marketplace, including third-party Designer Extensions
- Analyze, Optimize, and AEO (answer engine optimization)
- The
ask_webflow_aitool on the MCP server