# sdk_email_not_verified

> The sdk_email_not_verified Problem Details code: The user token needs email_verified set to true the first time this user signs in: the email is how the user is matched to a member.

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

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

## What the `detail` says

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

- The user token needs email_verified set to true the first time this user signs in: the email is how the user is matched to a member.

## Handling it

The request is well-formed but its values are not accepted; fix them before retrying.

## Example

```json
{
  "type": "https://docs.nexafone.so/errors/sdk_email_not_verified",
  "title": "Unprocessable Entity",
  "status": 422,
  "code": "sdk_email_not_verified",
  "detail": "The user token needs email_verified set to true the first time this user signs in: the email is how the user is matched to a member.",
  "requestId": "01J9Z8Q4TQ3W6M5V2X7Y8Z9A0B"
}
```

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