Integrating QuickEmailVerification with your own application will help you detect bad and fraudulent emails at the entry level. Read more about Real time email verification use cases.

To start with real-time email verification using QuickEmailVerification below are simple steps.

Create a API key

To use QuickEmailVerification API, first you will need to generate API key. Sign in to QuickEmailVerification and go to the "Api Settings". Click the "Add API Key" and enter a name for your api. Click on "Add" button and keep the generated API key, which is required to make QuickEmailVerification api requests.

API keys should be kept secret and avoid sharing it with others. Sharing QuickEmailVerification API keys will allow others to make QuickEmailVerification API calls using your verification credits.

Making a API request

QuickEmailVerification API requires two parameters

  • email : email to be verified
  • apikey : api key generated previously

API endpoint to send HTTP GET request for QuickEmailVerification API

API parameters should be passed as query string to a above given API end point.

API response information

A successful API call responds with the following values:

  • result string - The verified results will be: valid, invalid, unknown

  • reason 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
  • disposable true | false - true if the email address uses a disposable domain
  • accept_all true | false - true if the domain appears to accept all emails delivered to that domain
  • role true | false - true if the email address is a role address (,, etc)
  • email string - Returns a normalized version. ( ->
  • user string - The local part of an email address. ( -> niki)
  • domain string - The domain of the provided email address. ( ->
  • safe_to_send true | false - true if the email address is safe for deliverability
  • success true | false - true if the API request was successful
  • message 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 response codes for API request

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.

Example request and response

To verify a email, f.e, a request should be made like below

Which should response like below


PHP library for email verification

If you are a PHP developer, you can use QuickEmailVerification PHP library for email verification.

Check more details for PHP library at Github

Node.js library for email verification

Node.js developers can integrate QuickEmailVefication in their application using our Node.js library for email verification.

Read more about Node.js library at Github