invalid_user_token

View as Markdown llms.txt


HTTP status	`401`
Area	Keys and SDK sessions
Problem `type`	`https://docs.nexafone.so/errors/invalid_user_token`

The user token is not a valid HS256 JWT signed with one of the workspace’s (or partner’s) secret keys of the same mode as the publishable key, or a required claim (sub, jti, exp) is missing. See user tokens.

Handling it

Check the credential: send a valid, unrevoked key or a fresh token.

Example

{
  "type": "https://docs.nexafone.so/errors/invalid_user_token",
  "title": "Unauthorized",
  "status": 401,
  "code": "invalid_user_token",
  "detail": "A human-readable explanation of this occurrence.",
  "requestId": "01J9Z8Q4TQ3W6M5V2X7Y8Z9A0B"
}

Match on code, never on detail: the wording may change. See Problem Details.