Fetch API
Update Context
PATCH
Update the region and locale stored against a
contextKey. Subsequent requests that use the same token reflect the change — useful for region/language switching without minting a new token.
Scope is not changed via this endpoint. A scope transition (for example, an authenticated visitor moving from public to b2b after login) is handled server-side by issuing a new contextKey in the new scope.
Path Parameters
string
required
Your project’s Fetch token, embedded in the subdomain.
Headers
string
required
The
contextKey to update. 36–50 characters.string
Required when the project has fetch API keys configured.
Request Body
string
required
The new region key (e.g.
eu). Must be a region available within the token’s scope — see List Contexts.string
required
The new locale key (e.g.
de-DE). Must be one of the new region’s supported locales.Response
string
required
The updated region key.
string
required
The updated locale key.
string
required
The unchanged scope key (returned for reference).