If you are on a Customer.io EU account, construct the client with the EU region explicitly: new APIClient with region set to RegionEU. Without it every call hits the US endpoint, gets a 301 to the EU host, and the SDK surfaces it as an opaque Unknown error because it does not follow redirects. The redirect-following gap was patched in 3.5.1, but setting the right region avoids the redirect entirely and is required regardless.

Context: Issue customerio/customerio-node#134 (closed, 8 comments): Calls through the Node SDK failed with a bare 301 Unknown error. Another user dug into the response body and found wrong datacenter: the backend tried to redirect to the EU API host, but the SDK's request layer does not follow redirects. The maintainer confirmed the root cause was simpler than a redirect bug: the client defaults to the US region, and this user was on an EU account.

## Matched source
Source: Published skill
Original query: "Customer.io SDK 301 Unknown error: EU accounts must set the region explicitly"
Key terms: accounts, customer, error, explicitly, must, region, unknown
