Skip to content

Fix regional endpoints: account-scoped regions + correct 403 wording#380

Open
kabraham13 wants to merge 2 commits into
mainfrom
fix/regional-endpoints-account-region-scope
Open

Fix regional endpoints: account-scoped regions + correct 403 wording#380
kabraham13 wants to merge 2 commits into
mainfrom
fix/regional-endpoints-account-region-scope

Conversation

@kabraham13

@kabraham13 kabraham13 commented Jun 26, 2026

Copy link
Copy Markdown
Contributor

Fixes two inaccuracies in Regional API Endpoints that were reported as out of date.

1. Region applies to accounts, not keys

The Access requirements section said:

If your account has regional endpoint access, any API key can be used with any regional endpoint.

This is the inverse of how regional endpoints work, and undercuts the data-residency guarantee they exist to provide. Corrected to:

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.

2. The regional access error is a 403, not an "authentication" error

The Warning and Access requirements both called it a "403 authentication error." A request to a regional endpoint an account isn't assigned to actually returns:

HTTP 403 Forbidden
{"message":"Your account is denied access. ..."}

That's an authorization error, not authentication. Updated both references to "403 error (Your account is denied access)" and switched to present tense per the style guide.

Reviewed with the repo's docs-review workflow (editorial + Diataxis); both changes pass.

Reported by Mathias Hauser.

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.
@mintlify

mintlify Bot commented Jun 26, 2026

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
deepl-c950b784 🟢 Ready View Preview Jun 26, 2026, 1:42 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

…ion)

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.
@kabraham13 kabraham13 changed the title Fix regional endpoints: clarify region applies to accounts, not keys Fix regional endpoints: account-scoped regions + correct 403 wording Jun 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant