Skip to main content
GET
/
context
/
token
curl 'https://fetch-<project-token>.frontic.com/context/token' \
  -H 'fs-context: <context-key>'

{
  "token": "ae0d4981-c363-4d5a-a49e-1f053d49f2f7",
  "region": "eu",
  "locale": "de-DE"
}
Resolve a contextKey to the stored region, locale, and scope. Useful for hydrating client state from a cookie, or for verifying a token before making other requests.

​
Path Parameters

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

​
Headers

​
fs-context
string
required
The contextKey to resolve. The token must be 36–50 characters and exist in the project.
​
fs-secret
string
Required when the project has fetch API keys configured.

​
Response

​
token
string
required
The active contextKey.
​
region
string
required
The region key (e.g. eu, uk).
​
locale
string
required
The locale key (e.g. de-DE, en-GB).

​
Status codes

CodeWhen
200Token resolved
400INVALID_TOKEN — fs-context not in the 36–50 character range
401fs-secret missing or wrong (only when the project has fetch keys configured)
404TOKEN_NOT_FOUND — token doesn’t exist in this project
curl 'https://fetch-<project-token>.frontic.com/context/token' \
  -H 'fs-context: <context-key>'

{
  "token": "ae0d4981-c363-4d5a-a49e-1f053d49f2f7",
  "region": "eu",
  "locale": "de-DE"
}