Welcome to the EmailListVerify (ELV) Customer API documentation. This guide is designed for developers, system integrators, and API enthusiasts seeking to explore and utilize the features of the EmailListVerify API. Our API facilitates individual email address verification and supports batch verification through file uploads. Accessible as a publicly available REST API server, you can seamlessly integrate ELV into your workflows using HTTP requests with the programming or scripting language of your choice.
Overview
EmailListVerify aids in the verification of email address deliverability status. By using the tool, you can ensure the successful delivery of your campaign emails to intended recipients, or safeguard your registration process from fraudulent users. Our verification process directly employs the SMPT protocol to ensure the most up-to-date results. Verify emails individually or in bulk through the following tools:
- Single email verification: Quickly determine the deliverability status of a single email address, providing a simple introduction to ELV API.
- Bulk email verification: Upload a spreadsheet file with an email column for asynchronous verification, also referred to as an email list. Pre-screen deliverable emails before initiating your campaign. The formatting requirements are:
- The file format is .csv, .txt, or .xlsx
- One email address per row
- File does not exceed 100 MB
- Email addresses are placed in the same column
- The spreadsheet should not have more than 1,000,000 rows
- Find contact: Find a deliverable email based on a contact's first name, last name, and company domain. Alternatively, search for role-based emails of the company, such as info@company.com, or sales@company.com.
- Bulk find contact: Upload a spreadsheet file with columns denoting first name, last name, and company domain of contacts. This tool is only available in a web app at the moment, find more details here.
- The spreadsheet should not have more than 1,000 rows
- Disposable email check: Quickly determine if an email address is a temporary one. Suitable for registration processes.
Verification Steps
- DNS Check: Check the availability of the email domain by confirming the presence of a properly configured MX server, essential for receiving emails.
- Spamtrap Detection: Detect potential spam traps, which can harm sender's inbox health and reputation.
- Disposable Check: Ensure the email address is not generated for temporary use.
- Deliverability status: Utilize the SMTP protocol to verify the deliverability of email addresses.
- Accept all Handling: Detect risky email domains that accept messages sent to any username, potentially causing delivery issues.
- Error handling: Address anti-spam technology protection on SMTP servers and handle unexpected errors without exhausting any credits.
Deliverability status
The verification result of an email address can fall into one of the following categories:
| Result | Description |
|---|
ok | Indicates that the email address is valid and deliverable. |
email_disabled | Indicates that the email address is disabled or non-existent, resulting in bounced emails back to the sender. |
dead_server | Indicates that the email domain does not exist or lacks proper MX server configuration, leading to bounced emails back to the sender. |
invalid_mx | Indicates that the email domain has misconfigured MX servers, causing incoming emails to bounce back to the sender. |
disposable | Indicates that the email domain is associated with temporary email addresses that are short-lived, potentially resulting in bounced emails or reaching unintended recipients. |
spamtrap | Represents an email address designed as a decoy to attract and identify spam emails, potentially harming the sender's reputation. Incoming emails are delivered but flagged for monitoring. |
ok_for_all | Indicates that the email domain accepts all emails, regardless of the recipient's actual existence. Incoming emails may or may not bounce back to the sender. |
smtp_protocol | Signifies that the SMTP communication unexpectedly terminated before verifying deliverability status. No credits are deducted for this verification request. |
antispam_system | Indicates that the destination server's anti-spam measures prevented deliverability status verification. No credits are deducted for this verification request. |
unknown | Denotes an unknown error that prevented verification of email address deliverability. No credits are deducted for the verification request. |
invalid_syntax | Indicates that the input value lacks a valid email address syntax. No credits are deducted for this verification request. |
Verification quality
This feature is currently exclusive to bulk email verifications and is designed to reduce the occurrence of antispam_system, smtp_protocol, and unknown statuses. It reflects the level of verification accuracy for each email within the list. The available options are as follows:
- Standard: Represents our traditional verification quality, known for its quick and reliable results. Priced at 1 credit per email, the standard process includes multiple retry attempts from different IP addresses if encountering the specified statuses or unexpected errors.
- High: Introduces our advanced verification method, priced at 2 credits per email. This option offers twice the retries from varied IP addresses, which may lead to a slower verification process in extreme cases. However, it significantly reduces the likelihood of encountering the mentioned states. Additionally, the high-quality verification includes a new feature implementing greylisting, a proven anti-spam measure. Greylisting involves temporarily rejecting emails from certain senders, later allowing them through after a delay. In such instances, our system retries verification multiple times with varying delays, with a maximum delay of 30 minutes. While this may postpone the verification process for the entire email list by up to 30 minutes, it substantially increases the chances of converting antispam_system responses to ok or email_disabled statuses.
Authentication
Generate your API key in the API section before initiating API requests. All endpoints support two interchangeable authentication methods:
- Use the
x-api-key HTTP header (e.g., cOGs9KY3LNzxe3EBIJ6M5)
- Include the
secret query string parameter in the URL (e.g., secret=cOGs9KY3LNzxe3EBIJ6M5)
Credit Types and Usage
The standard pricing for email verification is typically 1 credit per verified email address, although this may vary depending on the specific tool being used. At EmailListVerify, we offer two types of credits that can be purchased through our pricing page. These credits differ in terms of how they are maintained and charged:
- On-Demand Credit: This option involves a one-time purchase of credits that never expire. You have the flexibility to use these credits at your convenience, but they do not automatically replenish. On-Demand credits are ideal for one-time verification needs or preparing for a specific email campaign.
- Daily Credit: Alternatively, you can opt for a subscription that provides a daily allocation of credits. Your credit usage is refreshed daily at midnight (UTC). Daily credits are well-suited for continuous verification requirements, such as validating user emails in real-time during registration processes.
Rate Limits
To ensure fair usage and maintain the stability of our API for all users, we enforce a rate limit of 15 requests per second. If you exceed this limit, your requests may be temporarily blocked until the rate limit resets. We recommend implementing proper error handling and retry logic in your application to manage this limit effectively.
Additional Resources
- JSON Documentation: Access a machine-readable JSON version of the EmailListVerify Customer API documentation, suitable for system integration or developers requiring a machine-readable format.