Email batch verification
Learn more about how to verify multiple email addresses in a single request.
Use the Email batch verification to verify multiple email addresses in one request. It is designed for bulk verification scenarios, such as scheduled cleanup jobs, large-scale validation, or onboarding workflows where you need to check many email addresses at once. Each email address is verified in real time, and the response returns verification results for each submitted value.
Note: This API does not update data in Reltio, so you can use it in external applications or validate email addresses before loading data into Reltio.
You can send up to 100 email addresses in a single request.HTTP method and endpoint
Use the following HTTP method and endpoint path to submit the request.
POST {EnvironmentURL}/reltio/api/{tenantId}/verification/email/_batchVerify{EnvironmentURL} with your Reltio environment URL. The following table describes the endpoint path parameters.
| Parameter | Type | Required | Description |
|---|---|---|---|
tenantId | String | Yes | The unique identifier of the tenant. Specifies the tenant context for the request. |
Request headers
The following request headers must be included.
| Header | Value | Required |
|---|---|---|
Authorization | Bearer <access_token> | Yes |
Content-Type | application/json | Yes |
Request body
The following table describes the request body parameters, including accepted values and defaults.
| Parameter | Type | Required | Description | Accepted values / Default |
|---|---|---|---|---|
email | String | Yes | The email address to verify. Each object in the array must include an email field. | Up to 100 records per request |
Example request
Use the following example to see how a complete request is structured with headers and a JSON body.
POST {EnvironmentURL}/reltio/api/{tenantId}/verification/email/_batchVerify
Authorization: Bearer <accessToken>
Content-Type: application/json
[
{"email": "jacob.evans27@gmail.com"},
{"email": "jane.smith2@gmail.com"}
]Response body
The following table describes the fields returned in the response body.
| Field | Type | Description |
|---|---|---|
Status | String | Verification result for the email address. Possible values include Valid, Invalid, or Unknown. |
Account | String | Email account name extracted from the address, when available. |
Domain | String | Domain part of the email address, such as example.com. |
IsDisposable | Boolean | Indicates whether the email address belongs to a disposable email provider. |
IsSystemMailbox | Boolean | Indicates whether the email address is a system-generated or non-user mailbox, such as noreply@example.com. |
EmailAddress | String | Email address that was verified. |
VerifiedOn | DateTime | Timestamp that shows when the verification was performed. |
RequestStatus | String | Result of the verification request for that email address. If verification fails, this field contains the status or error details for that record. |
Example response
The following example shows a response with one result object for each submitted email address.
[
{
"Status": "Valid",
"Account": "jacob.evans27",
"Domain": "gmail.com",
"IsDisposable": false,
"IsSystemMailbox": false,
"EmailAddress": "jacob.evans27@gmail.com",
"VerifiedOn": "2025-09-10T09:35:03.807Z",
"RequestStatus": "Success"
},
{
"Status": "Valid",
"Account": "jane.smith2",
"Domain": "gmail.com",
"IsDisposable": false,
"IsSystemMailbox": false,
"EmailAddress": "jane.smith2@gmail.com",
"VerifiedOn": "2025-09-10T09:35:03.807Z",
"RequestStatus": "Success"
}
]