Email Verification API Documentation

The RealPhoneValidation – Email Verification API uses GET/POST methods and supports only HTTPS with TLS v1.2+.

Required Input Parameters:

Emailemail address to verify
TokenUnique PW given by RealValidation

Response Fields:

Response FieldDescription
retval(See Appendix A below)
error_text(See Appendix A below)
status(See Appendix A below)
connected“Y” for yes, “N” for no (See Appendix A below)
disposable“Y” for yes, “N” for no (See Appendix A below)

Example: Successful Request

Result in XML

<?xml version=”1.0” encoding=”UTF-8”?>

Example: Unsuccessful Request

Result in XML

<?xml version=”1.0” encoding=”UTF-8”?>
  <error_text>invalid email address format</error_text>

Appendix A:

Retval CodeResponseMsgDescription
-1UnauthorizedToken not provided
-1invalid email address fomatThe email address is not formatted properly
-1server-unavailableServer issue — try again
-1timeoutThe response did not come back within the required time.
0Good Response
102invalid email address formatThe email address not formatted properly
connected“Y” for yes, “N” for noWhether or not a valid email is connected to active online networks
statusvalidThe email represents a real account / inbox available at the given domain
statusinvalidNot a real email
statusunknownThese are domains that respond to every verification request in the affirmative and, therefore cannot be fully verified.
statusaccept_allGood Response
error codeemail_address_invalidThe email is not formatted correctly
error codeemail_domain_invalidThe domain does not exist or is not capable of receiving email
disposable“Y” for yes, “N” for noThe email represents a real account/inbox available at the given domain
Email Verification API Doc
Email Verification API 060222

Before you go...

Are you currently using a
phone validation service?

Scroll to Top