Unsigned token

An unsigned token error indicates that the application requires signed tokens, but the X-Token provided in the request is unsigned.

Sign the token in your backend before forwarding it.

Response

All error responses follow the Problem Details (RFC 9457) format, which defines the type, title, status, detail, and instance fields.

Here is an example of the response returned for this error:

{  "type": "https://croct.help/api/authentication/unsigned-token",  "title": "The token is unsigned.",  "status": 401,  "detail": "The application requires a signed token, but an unsigned token was provided.",  "instance": "/client/web/content"}