From 4b2558be36f9a0682509e400701f67721efa3193 Mon Sep 17 00:00:00 2001 From: Kevin Abraham Date: Fri, 26 Jun 2026 09:34:57 -0400 Subject: [PATCH 1/2] Fix regional endpoints: clarify region applies to accounts, not keys The Access requirements section stated "any API key can be used with any regional endpoint." This is incorrect: API keys are not region-specific, but each account is restricted to a single region, so a key only works with the regional endpoint its account is assigned to. --- docs/getting-started/regional-endpoints.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/getting-started/regional-endpoints.mdx b/docs/getting-started/regional-endpoints.mdx index a0e06a5c..43dc9918 100644 --- a/docs/getting-started/regional-endpoints.mdx +++ b/docs/getting-started/regional-endpoints.mdx @@ -172,7 +172,7 @@ echo $result->text; Regional endpoints require activation through a regional deployment addendum. Requests to regional endpoints without activation will return a 403 authentication error. Contact your account manager or [reach out to our sales team](https://www.deepl.com/contact-us) to activate regional endpoints for your account. -If your account has regional endpoint access, any API key can be used with any regional endpoint. +While API keys are not region-specific, each DeepL account is restricted to a single region. Your keys work only with the regional endpoint your account is assigned to. ### API compatibility From d20d83f12ce4344bb7dce03e1788321961a7c09c Mon Sep 17 00:00:00 2001 From: Kevin Abraham Date: Fri, 26 Jun 2026 09:49:30 -0400 Subject: [PATCH 2/2] Correct regional-endpoint 403 wording (denied access, not authentication) The Warning and Access requirements sections described the regional access error as a "403 authentication error." A request to a regional endpoint the account isn't assigned to actually returns a 403 with message "Your account is denied access" (an authorization error, not authentication). Updated both references and switched to present tense per the style guide. --- docs/getting-started/regional-endpoints.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/getting-started/regional-endpoints.mdx b/docs/getting-started/regional-endpoints.mdx index 43dc9918..43c7d4d7 100644 --- a/docs/getting-started/regional-endpoints.mdx +++ b/docs/getting-started/regional-endpoints.mdx @@ -7,7 +7,7 @@ public: false DeepL offers regional API endpoints that process and store data within specific geographic regions. Regional endpoints provide the same API functionality as the standard endpoint, with data processing occurring in data centers located in specific regions. These endpoints help organizations meet data residency and compliance requirements, and can also reduce latency for users in specific geographic regions. -Regional endpoints are only available to customers who have signed a regional deployment addendum. Without a signed addendum, requests to regional endpoints will return a 403 authentication error. Contact your account manager or [reach out to our sales team](https://www.deepl.com/contact-us) to discuss access. +Regional endpoints are only available to customers who have signed a regional deployment addendum. Without a signed addendum, requests to regional endpoints return a 403 error. Contact your account manager or [reach out to our sales team](https://www.deepl.com/contact-us) to discuss access. ## Endpoint URLs @@ -170,7 +170,7 @@ echo $result->text; ### Access requirements -Regional endpoints require activation through a regional deployment addendum. Requests to regional endpoints without activation will return a 403 authentication error. Contact your account manager or [reach out to our sales team](https://www.deepl.com/contact-us) to activate regional endpoints for your account. +Regional endpoints require activation through a regional deployment addendum. Requests to regional endpoints without activation return a 403 error (`Your account is denied access`). Contact your account manager or [reach out to our sales team](https://www.deepl.com/contact-us) to activate regional endpoints for your account. While API keys are not region-specific, each DeepL account is restricted to a single region. Your keys work only with the regional endpoint your account is assigned to.