Skip to main content
PATCH
/
context
curl -X PATCH 'https://fetch-<project-token>.frontic.com/context' \
  -H 'fs-context: <context-key>' \
  -H 'Content-Type: application/json' \
  -d '{
    "region": "eu",
    "locale": "de-DE"
  }'

{
  "region": "eu",
  "locale": "de-DE",
  "scope": "public"
}
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

​
project-token
string
required
Your project’s Fetch token, embedded in the subdomain.

​
Headers

​
fs-context
string
required
The contextKey to update. 36–50 characters.
​
fs-secret
string
Required when the project has fetch API keys configured.

​
Request Body

​
region
string
required
The new region key (e.g. eu). Must be a region available within the token’s scope — see List Contexts.
​
locale
string
required
The new locale key (e.g. de-DE). Must be one of the new region’s supported locales.

​
Response

​
region
string
required
The updated region key.
​
locale
string
required
The updated locale key.
​
scope
string
required
The unchanged scope key (returned for reference).

​
Status codes

CodeWhen
200Context updated
400INVALID_TOKEN, INVALID_POST_BODY, or INVALID_PARAMETERS — token is malformed, body isn’t valid JSON, or region/locale aren’t a valid combination for the token’s scope
401fs-secret missing or wrong (only when the project has fetch keys configured)
404TOKEN_NOT_FOUND — token doesn’t exist in this project
curl -X PATCH 'https://fetch-<project-token>.frontic.com/context' \
  -H 'fs-context: <context-key>' \
  -H 'Content-Type: application/json' \
  -d '{
    "region": "eu",
    "locale": "de-DE"
  }'

{
  "region": "eu",
  "locale": "de-DE",
  "scope": "public"
}