Pricing
Apps
Log inStart free trial

Regions & base URLs

WEXTL data lives in a region you choose per organization. This guide covers regional hosts and how to handle a wrong-region response.

AI-assisted documentation

This documentation is compiled from our own product source code and internal specs, the platform's public API specification, and anonymized requests logs we collect from our support team[2].

Updates every sample URL on this page to your organization's regional host. Match the shard in your API key (wextl_<shard>_…).

A Personal Access Token is minted against the organization's region — you never need to pass a region parameter separately. The token prefix is wextl_<shard>_… (for example wextl_eu1_…). The TypeScript SDK derives https://<shard>.wextl.com/api/v1 from that prefix automatically.

Send API requests to your organization's regional host. Use the Region control at the top of any docs page to rewrite sample URLs. The exact hostname for your organization is also shown next to your key in the dashboard.

  • Europe (eu1) — REST https://eu1.wextl.com/api/v1, MCP https://eu1.wextl.com/api/mcp
  • United States (us1) — REST https://us1.wextl.com/api/v1, MCP https://us1.wextl.com/api/mcp
bash
curl https://eu1.wextl.com/api/v1/workflows \
  -H "Authorization: Bearer wextl_..."
text
https://eu1.wextl.com/api/mcp

If a request reaches the wrong regional host, the API returns HTTP 421 with a wrong_region error code and a base_url field pointing at the correct host. Well-behaved clients should retry the same request against that base_url rather than treating it as a hard failure. The TypeScript SDK does this automatically when followRegion is left at its default.

  1. WEXTL® regional routing and 421 wrong-region handling implementation.
  2. Our users' real cross-region API traffic.
  3. The OpenAPI specification's server list.