Elite EmailVerifier API

With the Elite Email Verifier API, you get the unique ability to verify thousands of email addresses in real-time. It has been built for optimization and includes a single endpoint for fast lookups. Its simplicity makes it easy to integrate into any application, without having to worry about thousands of lines of code or complex configurations.

Responses

A JSON format is used to receive all data. A success parameter is included in each response sent from the API. This parameter indicates whether or not the request was successful, with 1 being successful and 0 being unsuccessful. Optionally, an error (string) parameter can be provided when success is 0. As long as success is 1, the response will always be encapsulated in an EmailVeriifier parameter.

Here are JSON responses for Successful and Error Response

Success response JSON schema:

							  
	  HTTP/1.1 200 OK
	{
	   "email_verifier":{
		  "email":"john.doe@dmail.com",
		  "code":"5",
		  "role":"false",
		  "free_email":"true",
		  "result":"Safe to Send",
		  "reason":"Deliverable",
		  "send_transactional":"1",
		  "did_you_mean":""
	   },
	   "success":"1",
	   "balance":"1725935"
	}
	
	
						  

							  
   HTTP/1.1 401 Unauthorized
	
	{
	"email_verifier":{
	  "error":"Wrong API",
		"code":"0"
   },
   "success":"0"
	} 
	
						  

Security

Elite EmailVerifier's APIs are all rate-limited to ensure the stability and fairness of our platform. Developers are asked to limit calls, cache results, and retry requests responsibly according to industry standards. There can be a maximum of 10 concurrent calls (parallel connections). With a higher validation speed, you'll receive the following error:

							  
  HTTP/ 429 Too Many Requests
  
  {
	 "email_verifier":{
		"error":"Maximum concurrent calls reached",
		"code":"0"
	 },
	 "success":"0"
  }
   
 

Public API Key

Codes in JavaScript can be used to access the public API key which starts with public_. Your domain URL must be added to the approved CORS domain list of the API key in order to use it.

When you create your public API key, we ask you to create a list of trusted domains in order to prevent abuse. Requests made with a public API key will only work if they come from a trusted domain. Requests will also be limited to 20 per day per user.

You will get the following error if you attempt to validate more than 20 emails with the same internet IP address:

								  
	  HTTP/ 429 Too Many Requests
	   {
	  "email_verifier":{
			"error":"Authentication Failed - The maximum number of calls per day reached."
		  },
	  "success":"0"
		  }
	  
	  

Bulk validation API

The bulk validation API can validate a single list at a time. You can queue your bulk API job and it will run automatically once your first job is completed if you already uploaded and started a list using the list upload feature on Emailverifier.

STATUS CODES

Elite EmailVerifier API uses following status codes:

Single Validation

Verify one email at a time. You may retry a verification request up to five times if it takes longer than the timeout. Any further requests will count against your usage after 5 minutes have passed. When the verification results are available, you will be notified.

A random sample response will be returned when a test key is used.

HTTP GET Request:

Parameters for Single validation:

Response

Curl

			
	curl --request GET \
	     --url https://api.emailverifier.co/v1/ \
		 --header 'Accept: application/json' 	
	
								

								  
	   HTTP/1.1 200 OK
  {
	 "email_verifier":{
		"email":"john@dmail.com",
		"code":"5",
		"role":"false",
		"free_email":"true",
		"result":"Safe to Send",
		"reason":"Deliverable",
		"send_transactional":"1",
		"did_you_mean":""
	 },
	 "success":"1",
	 "balance":"1926545"
  }
  
							  

Python

								  
  
	  import requests
  
	  url = "https://api.emailverifier.co/v1/"
	  
	  headers = {"Accept": "application/json"}
	  
	  response = requests.request("GET", url, headers=headers)
	  
	  print(response.text)
  
							  

							  
	  HTTP/1.1 200 OK
	  {
	 "email_verifier":{
		"email":"john.doe@dmail.com",
		"code":"5",
		"role":"false",
		"free_email":"true",
		"result":"Safe to Send",
		"reason":"Deliverable",
		"send_transactional":"1",
		"did_you_mean":""
		},
	  "success":"1",
	  "balance":"1725935"
	  }
	  
	  

PHP

	 
		
	request('GET', 'https://api.emailverifier.co/v1/', 
	['headers' => [
	'Accept' => 'application/json',
	 ],
	]);
	echo $response->getBody();
	  
  

	 
	HTTP/1.1 200 OK
		{
  "email_verifier":{
     "email":"john.doe@dmail.com",
	  "code":"5",
	  "role":"false",
	  "free_email":"true",
	  "result":"Safe to Send",
	  "reason":"Deliverable",
	  "send_transactional":"1",
	  "did_you_mean":""
	},
 "success":"1",
     "balance":"1725935"
	}
		  
	

NodeJS

  
const fetch = require('node-fetch');

const url = 'https://api.emailverifier.co/v1/';
const options = {method: 'GET', headers: {Accept: 'application/json'}};

fetch(url, options)
  .then(res => res.json())
  .then(json => console.log(json))
  .catch(err => console.error('error:' + err));
		  
  

									  
HTTP/1.1 200 OK
	{
	  "email_verifier":{
		  "email":"john.doe@dmail.com",
		  "code":"5",
		  "role":"false",
		  "free_email":"true",
		  "result":"Safe to Send",
		  "reason":"Deliverable",
		  "send_transactional":"1",
		  "did_you_mean":""
	 },
	   "success":"1",
	   "balance":"1725935"
	}
	 
		

Bulk Validation

Verify a batch of emails. Separate each email using a comma and send it as a parameter email. A batch can consist of up to 50,000 emails.

It is possible to encode data using application/x-www-form-urlencoded, multipart/form-data, or application/json. All parameters should be sent in the HTTP request body, not in the URL query string.

Upon batch completion, the results will be sent to that URL via HTTP POST. As with the batch status endpoint below (GET /v1/batch), the body will be JSON data. A successful batch creation response with an example batch id will be returned when a test key is used. Furthermore, the simulate parameter can be utilized to simulate certain API responses in conjunction with a test key.

HTTP Request:

Parameters

Response

Status Codes

With the "id" parameter specified as the request parameter, the batch endpoint will return the current status of the batch verification job.

The billing related messages will be returned if an error occurs when a credit card transaction is needed to obtain enough credits to verify a batch. A 402 response code will be returned.

A random sample response will be returned for each email in the batch when a test key is used. A test key can also simulate certain API responses by utilizing the simulate parameter. The batch status endpoint will no longer return individual email verification results after 30 days. Instead, aggregate counts will be returned.

HTTP Status Codes

HTTP Request:

Parameters:

Response: