Official Email Validation API library client for Node.js
QuickEmailVerification provides the quickest way to avoid fake / invalid emails.
- Get actual users by scanning email address.
- Remove invalid, dead and fake emails from your email list.
- Save time and money by sending mail to actual users.
Let's Get Started
email - (string) This is a email address you need to verify. It should be url encoded.
apikey - (string) This is the key you generated from "api settings" page.
NOTE: Keep API key with you. - you'll need it to setup the client as explained below.
Make sure you have npm installed.
$ npm install quickemailverification
Works with [ 0.8 / 0.9 / 0.10 / 0.11 ]
var quickemailverification = ;// PRODUCTION MODEquickemailverification;
A successful API call responds with the following values:
string- The verified results will be:
string- Reason definitions are as below:
invalid_email- Specified email has invalid email address syntax
invalid_domain- Domain name does not exist
rejected_email- SMTP server rejected email. Email does not exist
accepted_email- SMTP server accepted email address
no_connect- SMTP server connection failure
timeout- Session time out occurred at SMTP server
unavailable_smtp- SMTP server is not available to process request
unexpected_error- An unexpected error has occurred
no_mx_record- Could not get MX records for domain
temporarily_blocked- Email is temporarily greylisted
exceeded_storage- SMTP server rejected email. Exceeded storage allocation
true | false- true if the email address uses a disposable domain
true | false- true if the domain appears to accept all emails delivered to that domain
true | false- true if the email address is a role address (
true | false- true if the email address is from free email provider like Gmail, Yahoo!, Hotmail etc.
string- Returns a normalized version. (
string- The local part of an email address. (
string- The domain of the provided email address. (
string- The preferred MX record of email domain. This field contains empty string when MX record is not available.
string- The domain name of the MX host. This field contains empty string when MX record is not available.
true | false- true if the email address is safe for deliverability
string- Returns email suggestions if specific typo errors found in email
true | false- true if the API request was successful
string- Describes API call failure reason
HTTP Response headers
Total remaining credits can be found by http response header. It contains overall remaining credits, including Persistent & Per day credits.
- X-QEV-Remaining-Credits - Your remaining email verification credits (i.e. Per Day credits + Persistent Credits).
HTTP status codes for QuickEmailVerification API calls
QuickEmailVerification API also returns following HTTP status codes to indicate success or failure of request.
200- Request is completed successfully
400- Server can not understand the request sent to it. This is kind of response can occur if parameters are passed wrongly.
401- Server can not verify your authentication to use api. Please check whether API key is proper or not.
402- You are running out of your credit limit.
404- Requested API can not be found on server.
429- Too many requests. Rate limit exceeded.
QuickEmailVerification single email verification API sandbox mode helps developers to test their integration against simulated results. Requesting against sandbox endpoint is totally free and no credits will be deducted from actual credit quota.
Please refer our knowledge base to learn more about sandbox mode.