Email Verification API Reference

This API is organized around REST. Our API has predictable resource-oriented URLs, accepts form-encoded request bodies, returns JSON-encoded responses, and uses standard HTTP response codes, authentication, and verbs.

Authentication

Email Verification API uses Rapid API keys to authenticate requests.

Your API keys carry many privileges, so be sure to keep them secure! Do not share your secret API keys in publicly accessible areas such as GitHub, client-side code, and so forth.

Implementation differs with each programming language.

All API requests must be made over HTTPS. Calls made over plain HTTP will fail. API requests without authentication will also fail.

Endpoints

GET /check

var myHeaders = new Headers();
myHeaders.append("X-RapidAPI-Key", "{API-KEY}");
myHeaders.append("X-RapidAPI-Host", "email-validation-and-verification-end-to-end-checks.p.rapidapi.com");

var requestOptions = {
  method: 'GET',
  redirect: 'follow',
  headers: myHeaders
};

fetch("https://email-validation-and-verification-end-to-end-checks.p.rapidapi.com/check?email={email}", requestOptions)
  .then(response => response.text())
  .then(result => console.log(result))
  .catch(error => console.log('error', error));

GET /{email}

var myHeaders = new Headers();
myHeaders.append("X-RapidAPI-Key", "{API-KEY}");
myHeaders.append("X-RapidAPI-Host", "email-validation-and-verification-end-to-end-checks.p.rapidapi.com");

var requestOptions = {
  method: 'GET',
  redirect: 'follow',
  headers: myHeaders
};

fetch("https://email-validation-and-verification-end-to-end-checks.p.rapidapi.com/{email}", requestOptions)
  .then(response => response.text())
  .then(result => console.log(result))
  .catch(error => console.log('error', error));

---

Returns

Below is a sample response from the endpoint

{
  "can_connect_smtp": false,
  "domain": "example.com",
  "email": "jane.doe@example.com",
  "is_catch_all": false,
  "syntax_valid": true,
  "typo": true,
  "is_disposable": true,
  "mx_accepts_email": true,
  "is_deliverable": false
}

---

Rate Limiting

Each subscription has its own rate limit. When you become a subscriber, you start by choosing a rate limit that suits your usage needs. Do not worry; You can upgrade or downgrade your plan at any time. For this reason, instead of starting with a larger plan that you do not need, we recommend you upgrade your plan after you start with “free” or “Pro plan” options and start using the API.

When you reach a rate limit (both daily and monthly), the service will stop responding and returning the HTTP 429 response status code (Too many requests).

A reminder email will be sent to you when your API usage reaches both 80% and 90%, so that you can take immediate actions such as upgrading your plan in order to prevent your application using the API from being interrupted.

You can contact our support unit if you need any assistance with your application regarding handling.

Error Codes

HulkHire uses standard HTTP response codes to indicate the success or failure of an API request. In general: Codes in the 2xx range indicate success. Codes in the 4xx range indicate a clientside error, which means that failed given the information provided (e.g., a missing parameter, unauthorized access etc.). Codes in the 5xx range indicate an error with HulkHire’s servers (normally this shouldn’t happen at all).

If the response code is not 200, it means the operation failed somehow and you may need to take action accordingly. You can check the response (which will be in JSON format) for a field called ‘message’ that briefly explains the error reported.

Status Code	Description
400	Bad Request The request was unacceptable, often due to missing a required parameter.
401	Unauthorized No valid API key provided.
404	Not Found The requested resource doesn’t exist.
429	Too many requests API request limit exceeded. See section Rate Limiting for more info.
5xx	Server Error We have failed to process your request. (You can contact us anytime)