This endpoint allows you to submit an email for validation and immediately returns a 202 response with a requestId.
The validation result will be sent to your configured webhook endpoint once processing is complete.
This is recommended for bulk validations or when you don't need immediate results.
Webhook Configuration
Your webhook endpoint must be configured prior to making the first request - this is something your success manager will help you set up during onboarding.
The validation result will be sent as a POST request to your webhook URL.
Webhook Payload
The webhook will receive a POST request with the validation result. See the WebhookPayload schema for the complete structure.
Example payload:
{
"allegrowStatus": "safe",
"domain": {
"isCatchAll": false,
"mxProvider": "google",
"mxRecords": ["aspmx.l.google.com", "alt1.aspmx.l.google.com"],
"name": "example.com"
},
"email": "[email protected]",
"mailbox": {
"isRoleAccount": false
},
"metadata": {
"unmodifiedPayload": "that you submitted on your initial call"
},
"requestId": "550e8400-e29b-41d4-a716-446655440000",
"result": {
"status": "safe",
"subStatus": "primary"
},
"validatedAt": "2026-04-22T10:30:00Z"
}Note: allegrowStatus is deprecated and mirrors the value of result.status. It will continue to be returned for backward compatibility but will be removed in a future release — please migrate to reading result.status.
See Validation Statuses for the meaning of each domain / mailbox field.
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
This endpoint allows you to submit an email for validation and immediately returns a 202 response with a requestId.
The validation result will be sent to your configured webhook endpoint once processing is complete.
This is recommended for bulk validations or when you don't need immediate results.
If you'd rather not configure a webhook, you can poll Validate Email Status using the requestId returned in the 202 response instead.
Response
The immediate response acknowledges receipt of the request. The actual validation result is delivered later to your webhook (see below).
{
"requestId": "550e8400-e29b-41d4-a716-446655440000",
"message": "Email validation request accepted"
}The requestId uniquely identifies this validation request and is included in the webhook payload delivered when processing completes.
Webhook Configuration
Your webhook endpoint must be configured prior to making the first request - this is something your success manager will help you set up during onboarding.
The validation result will be sent as a POST request to your webhook URL.
Webhook Payload
The webhook will receive a POST request with the validation result. See the WebhookPayload schema for the complete structure.
Example payload
{
"allegrowStatus": "safe",
"domain": {
"isCatchAll": false,
"mxProvider": "google",
"mxRecords": ["aspmx.l.google.com", "alt1.aspmx.l.google.com"],
"name": "example.com"
},
"email": "[email protected]",
"mailbox": {
"isRoleAccount": false
},
"metadata": {
"unmodifiedPayload": "that you submitted on your initial call"
},
"requestId": "550e8400-e29b-41d4-a716-446655440000",
"result": {
"status": "safe",
"subStatus": "primary"
},
"validatedAt": "2026-04-22T10:30:00Z"
}Note: metadata can have a maximum size of 32KB.
Deprecation notice
allegrowStatus is deprecated. It will continue to be returned alongside result.status with the same value for backward compatibility, but will be removed in a future release. Please migrate your integrations to read result.status instead.
About subStatus
subStatusresult.subStatus provides additional context on valid emails. Value is null if no sub-status was determined. See Validation Statuses for all possible values.
About validatedAt, domain, and mailbox
validatedAt, domain, and mailboxEvery webhook delivery includes a domain object (with name, mxProvider, mxRecords, and isCatchAll) and a mailbox object (with isRoleAccount), plus a validatedAt timestamp. See Validation Statuses for the meaning of each field.