Working with EU Hosting
EU Hosting gives Enterprise customers Webflow workspaces in a separate EU region. If your app or integration serves those customers, it needs to call the EU region with EU credentials.
This guide shows how to build an app that supports both the US and EU regions. For the host names and the features available in each region, see EU Hosting.
How regions affect your app
The Data API is the same in both regions, so your API calls don’t change. What changes is where you send them and which credentials you use:
- Each workspace, site, and user account belongs to one region.
- Each region needs its own registration of your app, with its own client ID and client secret.
- An access token works only with the API of the region that issued it.
So your app needs to know each user’s region and run OAuth in that region. It also needs to store the region with the token, and send every request to that region’s API.
As in the US region, a new EU registration is available only to users in your app’s workspace. External users can’t authorize it until Webflow approves it. The Webflow Marketplace isn’t available in the EU region, so ask your Webflow contact how to get your EU registration approved.
Build a region-aware app
These steps use JavaScript with Express. The same approach works in any language.
Register your app in each region
Register your app on webflow.com as usual. Then register it again from a workspace on eu.webflow.com. Use the same scopes, and set a redirect URI for your app.
Store the client ID, client secret, and redirect URI for each region as separate environment variables:
Define the regions in one place
Keep the hosts and credentials for each region in one object, so the rest of your code only passes a region key around:
Ask the user for their region
A user with an EU account can’t sign in through the US authorization page, so ask for the region before you start OAuth. For example, show two buttons:
Start OAuth in the user's region
Send the user to the authorization page for the region they chose. Save the region with the state value, so your callback knows which region issued the code:
Exchange the code in the same region
Exchange the authorization code at the token endpoint of the region that issued it, with that region’s client ID and client secret. Then store the region with the access token:
saveConnection stands for your own storage. Keep the access token encrypted, as you would for any OAuth token.
The SDK OAuth helpers, such as WebflowClient.authorizeURL and WebflowClient.getAccessToken, always use the US hosts. Build the authorization URL and request the token yourself, as these steps show.
Call the API in the connection's region
When you call the API, create the client with the base URL of the connection’s region:
For the Python SDK setup, see SDKs on the EU Hosting page.
Use site and workspace tokens
Scripts and internal integrations often use a site token or workspace token instead of OAuth. For an EU site, create the token in the site or workspace settings on eu.webflow.com. Then send your requests to https://api.eu.webflow.com/v2.
Handle EU links and assets
Your app may show links into Webflow or store asset URLs from the API. For EU users:
- Link to
eu.webflow.com, notwebflow.com, for pages such as the dashboard. - Expect asset URLs on
cdn.prod.eu.website-files.com. Don’t assume the US asset host when you parse or check asset URLs.
Test your integration
EU workspaces are invite-only. To test your app, ask your Webflow contact for access to an EU workspace. Then check that:
- You can connect an EU workspace through the EU flow, and a US workspace through the US flow.
- Requests for EU connections go to
api.eu.webflow.com, and requests for US connections go toapi.webflow.com. - Links and asset handling work for EU sites.
Troubleshooting
Next steps
- EU Hosting: host names, MCP, CLI, and what isn’t available in the EU region
- OAuth: the full OAuth flow
- Production EU authentication: use the Webflow CLI with an EU workspace