token_missing: No browser token was presented
A widget route under /widgets/v1/ was called without a widget token as its Bearer token. The widget routes take only a short-lived token minted by the app's server, never an API key. The budget link, portal and top-up pages carry their token in the link itself, so in practice only the widget routes answer this code.
What to do
- End users: open the link the service gave you, or ask it for a new one.
- Developers: mint the token server-side and pass it to the page; see widgets, budget links and the portal.
On the wire
HTTP 401, error type authentication_error. The widget routes always answer JSON, never an HTML page. The body depends on who answers.
A single-tenant (self-hosted) core answers:
{
"error": "unauthorized",
"errorDetail": {
"type": "authentication_error",
"code": "token_missing",
"message": "no token presented",
"param": null,
"doc_url": "…/developers/widgets.md#token-missing",
"fix": "send the short-lived token minted by the app's server (never an API key)"
}
}
The multi-tenant hosted front door checks for the token before the request reaches the account's core, and answers:
{
"error": "token_missing",
"errorDetail": {
"type": "authentication_error",
"code": "token_missing",
"message": "no token presented",
"param": null,
"doc_url": "…/errors/token_missing.md",
"fix": "open the link the service gave you, or ask it for a new one"
}
}
See all error codes.