# user_token_expired

> The user_token_expired Problem Details code: The token’s exp has passed, or lies more than 10 minutes ahead.

Source: https://docs.nexafone.so/v1/errors/user_token_expired/

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

The token’s `exp` has passed, or lies more than 10 minutes ahead. Sign a new token for every sign-in, just before the SDK asks for it.

## What the `detail` says

The `detail` explains the occurrence; it can read, for example:

- The user token has expired. Sign a new one.

## Handling it

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

## Example

```json
{
  "type": "https://docs.nexafone.so/errors/user_token_expired",
  "title": "Unauthorized",
  "status": 401,
  "code": "user_token_expired",
  "detail": "The user token has expired. Sign a new one.",
  "requestId": "01J9Z8Q4TQ3W6M5V2X7Y8Z9A0B"
}
```

Match on `code`, never on `detail`: the wording may change. See [Problem Details](/v1/errors/).