The Email Verification API is perfect for marketing campaigns that demand valid and verified emails. It allows your to send a bulk email list in the form of a CSV string and return the results in JSON.
The endpoint for the Email Verification API is
https://leadhootz-email-verification.p.rapidapi.com/api/emailvalidation?emails=
We charge per record retrieved. Each person record in the data array of the response counts as a single credit against your total package.
See Authentication and Requests to learn how to input requests. We recommend using a JSON object to capture request parameters and will do so in the examples.
The current default rate limit is 10 requests per minute.
When querying the API in URL, you can add data points to a queried person as key/value pairs at the end of the request string.
You can also click on the individual parameter names in the table below to view more information on them.
PARAMETER NAME | DESCRIPTION | EXAMPLE |
---|---|---|
emails | The comma separated list of emails. | https://leadhootz-email-verification.p.rapidapi.com/api/emailvalidation?emails=[email protected],[email protected],[email protected] |
When you execute an Email Verification API request with more than a single email, we process these in parallel. This means that the request response time will be based on the longest performing email in the list.
You can also click the field names in the table below to view more information on them.
FIELD | DESCRIPTION | TYPE |
---|---|---|
success | True/False value indicating whether the requests was successful or not | Boolean |
responseType | Value indicating the type of response used | Integer |
jsonValue | The Json string that comprises the response collection of emails verified. | String |
valid | The total valid emails in the response | Integer |
invalid | The total invalid emails in the response | Integer |
_retries | The number of retries required if any. | Integer |
_startTime | The request start time. | DateTime |
_endTime | The request finish time. | DateTime |
_isValid | True/False value indicating whether the email is valid or not. | Boolean |
_emailAddress | The email address that was used. | String |
_domain | The domain within the email address that was used. | String |
_user | The actual response from the mail provider. | String |
_domainNoTld | ||
_mxRecords | The MX records that were found during the verification. | String |
_mailServer | The Mail service that was used for the verification. | String |
_options | The options that were used for the verification. | |
_status | The status Id of the verification outcome. | String |
_statusMessage | The status message of the verification outcome. | String |
_contactId | The contactId that can be provided as a reference for your own purposes. | Integer |
Here is an example response from the Email Verification API:
{ "success": true, "responseType": 1, "jsonValue": "[{ "_retries": 0, "_startTime": "2024-11-02T12:53:55.4137857+00:00\", "_endTime": "2024-11-02T12:53:55.4137884+00:00", "_isValid": false, "_emailAddress": "[email protected]", "_domain": "scottishpower.com", "_user": "The user \"karen.wright\" does not have a valid mailbox on \"scottishpower.com\". Please enter a valid email address.\", "_domainNoTld": "", "_emailSentence": "", "_mxRecords": [], "_mailServer": "iberdrola.in.tmes.trendmicro.eu", "_options": [], "_status": 14, "_statusMessage": "Mailbox Check", "_contactId": "", "valid": 0, "invalid": 3 }
Cookie Notice
We and third parties such as our customers, partners, and service providers use cookies and similar technologies (\"cookies\") to provide and secure our Services, to understand and improve their performance, and to serve relevant information. For more information, see our Cookie Policy.