Skip to main content

Email Verification

Email verification can contain details such as whether an email is valid/invalid as well as if it's disposable and role based.

Minimum Requirements​

The following table lists the minimum inputs required to make a valid request for an Email Verification Check:

ResponseDescription
Email AddressFully formed email address

Service Request​

To request for an Email Verification, add a EMAIL_VERIFICATION action to the request body entity PeopleActionsRequest:

{
"actions": [
{ "action": "EMAIL_VERIFICATION" }
]
}

PeopleActionsRequest​

Array of objects (PersonAction)

Actions to run with the given criteria

object (PersonRequest)

Person format used across the Investigate API

object (Address)

Address format used across the Investigate API

cohabitants
Array of strings (Cohabitants)

Cohabitants at given address

sourceYears
Array of integers <int32> (SourceYears) [ items <int32 > ]

Years when the matching datasets stored by GBG were issued. This could support customers compliance requirements.

tags
Array of strings

Free text tags for tracking purposes.

{
  • "actions": [
    ],
  • "person": {
    },
  • "address": {
    },
  • "cohabitants": [
    ],
  • "sourceYears": [
    ],
  • "tags": [
    ]
}

Service Response​

As part of the PersonActionsResponse entity, the property emailVerification contains the results of the request.

EmailVerificationActionResponse​

Array of objects (EmailVerificationAction)
object (Meta)

Metadata describing the response produced.

{
  • "result": [
    ],
  • "meta": {
    }
}

If no Email Verification has been requested, the response is empty.

If an Email Verification has been requested, the following response is available:

Description
emailVerificationemailThe email address supplied
resultThe response is based on the status supplied through the Contact Verification Result.