---
title: "identity.email-verified-check-request@1 · OpenVibe.Services"
canonical: "https://openvibe.services/docs/contracts/identity.email-verified-check-request"
updated: null
---

# identity.email-verified-check-request@1 · OpenVibe.Services

HTML: [identity.email-verified-check-request@1 · OpenVibe.Services](https://openvibe.services/docs/contracts/identity.email-verified-check-request)

# Check a person's verified email address `identity.email-verified-check-request@1`

Generated at 2026-11-13 06:25:48 UTC from [`openvibe-contracts v0.419.0`](https://github.com/OpenVibers/OpenVibe.Contracts/tree/v0.419.0) and [`openvibe-sdk v0.161.0`](https://github.com/OpenVibers/OpenVibe.SDK/tree/v0.161.0).

- Version: 1.0.0
- Owner: network
- Visibility: public
- Status: active
- Compatibility: backward
- Schema: [`https://openvibe.network/contracts/identity/email-verified-check-request.v1.json`](/docs/contracts/identity.email-verified-check-request.json)

A service with identity.emails.read asks whether one supplied email address is verified for one Network subject. The response never reveals address lists or whether an unknown subject exists.

## Fields

| Field | Type | Required | Description | Constraints |
| --- | --- | --- | --- | --- |
| `subject` | string | yes |  | - `pattern ^usr_[0-9A-HJKMNP-TV-Z]{26}$` |
| `email` | string | yes |  | - `format email`<br>- `maxLength 254` |

## Examples

From the contract's own test fixtures: valid ones validate, rejected ones must fail.

 Valid: owned-address

~~~~
{
  "subject": "usr_01JAB2C3D4E5F6G7H8J9K0MNPQ",
  "email": "alice@example.test"
}
~~~~

Rejected: no-address

~~~~
{
  "subject": "usr_01JAB2C3D4E5F6G7H8J9K0MNPQ"
}
~~~~

## Validate

~~~~
const contracts = require('openvibe-contracts');
contracts.validate('identity.email-verified-check-request@1', value);   // { valid, errors: [{ path, message }] }
~~~~