https://emailvalidation.abstractapi.com/v1/
? api_key = YOUR_API_KEY
& domain = eric@abstractapi.com
{
"email": "eric@abstractapi.com",
"autocorrect": "",
"deliverability": "DELIVERABLE",
"quality_score": 0.80,
"is_valid_format": true,
"is_free_email": false
"is_disposable_email": false
"is_role_email": false
"is_catchall_email": true
"is_mx_found": true
"is_smtp_valid": true
}
STARTER
$9
per
month
PRO
$49
per
month
SCALE
$99
per
month
The Email Validation and Verification API, like all of Abstract's APIs, is organized around REST. It is designed to use predictable, resource-oriented URL's and to use HTTP status codes to indicate errors.
The Email Validation and Verification API requires all communications to be secured TLS 1.2 or greater.
All of Abstract's API are versioned. The Email Validation and Verification API is currently on Version 1.
Your API key is your unique authentication key to be used to access Abstract's Exchange Rate API. Note that each of Abstract's API has a unique API key, so you will need different keys to access the Email Validation and Verification and IP Geolocation APIs, for example. To authenticate your requests, you will need to append your API key to the base URL.
https://emailvalidation.abstractapi.com/v1/
Abstract's Email Validation and Verification API requires only your unique API key and a single email:
https://emailvalidation.abstractapi.com/v1/
? api_key = YOUR_UNIQUE_API_KEY
& email = johnsmith@gmail.com
This was a successful request, and all available details about that email were returned:
{
"email": "johnsmith@gmail.com",
"autocorrect": "",
"is_valid_format": true,
"is_free_email": true,
"is_disposable_email": false,
"is_role_email": false,
"is_catchall_email": false,
"is_mx_found": true,
"is_smtp_valid": true,
"quality_score": 0.99,
}
PARAMETER
TYPE
DETAILS
api_key required
String
Your unique API key. Note that each user has unique API keys for each of Abstract's APIs, so your Exchange Rate API key will not work for as your IP Geolocation API key, for example.
email required
String
The email address to validate.
The API response is returned in a universal and lightweight JSON format.
PARAMETER
TYPE
DETAILS
email
String
The value for "email" that was entered into the request.
auto_correct
String
If a typo has been detected then this parameter returns a suggestion of the correct email (e.g., johnsmith@gmial.com => johnsmith@gmail.com). If no typo is detected then this is empty.
is_valid_format
Boolean
Is true if the email follows the format of "address @ domain . TLD". If any of those elements are missing or if they contain extra or incorrect special characters, then it returns false.
is_free_email
Boolean
Is true if the email's domain is found among Abstract's list of free email providers (e.g., Gmail, Yahoo, etc).
is_disposable_email
Boolean
Is true if the email's domain is found among Abstract's list of disposable email providers (e.g., Mailinator, Yopmail, etc).
is_role_email
Boolean
Is true if the email's local part (e.g., the "to" part) appears to be for a role rather than individual. Examples of this include "team@", "sales@", info@", etc.
is_catchall_email
Boolean
Is true if the domain is configured to catch all email.
is_mx_found
Boolean
Is true if MX Records for the domain can be found.
is_smtp_valid
Boolean
Is true is the SMTP check of the domain was successful.
quality_score
Number
An internal decimal score between 0.01 and 0.99 reflecting Abstract's confidence in the quality and deliverability of the submitted email.
In the example below, we show the request and response when the API detects a possible misspelling in the requested email.
Note that even if a possible misspelling is detected, all of the other checks on that email (e.g., free email, disposable domain, etc) will still be done against the original submitted email, not against the autocorrected email.
https://emailvalidation.abstractapi.com/v1/
? api_key = YOUR_UNIQUE_API_KEY
& email = johnsmith@gmial.con
The request was valid and successful, and so it returns the following:
{
"email": "johnsmith@gmial.con",
"autocorrect": "johnsmith@gmail.com",
"is_valid_format": true,
"is_free_email": true,
"is_disposable_email": false,
"is_role_email": false,
"is_catchall_email": false,
"is_mx_found": false,
"is_smtp_valid": false,
"quality_score": 0.13,
}
In the example below, we show the request and response for an email does not follow the proper format. If the email fails the is_valid_format check, then the other checks (e.g., is_free_email, is_role_email) will not be performed and will be returned as false
https://emailvalidation.abstractapi.com/v1/
? api_key = YOUR_UNIQUE_API_KEY
& email = johnsmith
The request was valid and successful, and so it returns the following:
{
"email": "johnsmith",
"autocorrect": "",
"is_valid_format": false,
"is_free_email": false,
"is_disposable_email": false,
"is_role_email": false,
"is_catchall_email": false,
"is_mx_found": false,
"is_smtp_valid": false,
"quality_score": 0.00,
}
Whenever you make a request that fails for some reason, an error is returned also in the JSON format. The errors include an error code and description, which you can find in detail below.
CODE
TYPE
DETAILS
200
OK
Everything worked as expected.
400
Bad request
Bad request
401
Unauthorized
The request was unacceptable. Typically due to the API key missing or incorrect.
500
Internal Server Error
The request could not be completed due to an error on the server side.
503
Service Unavailable
The server was unavailable.
The Abstract email verification API takes an email address and identifies whether it is valid or not, and how risky we think it will be. This real-time or asynchronous capability will help you detect and suppress any invalid or disposable email addresses, which will help clean your email list, reduce your bounce rate, and thus improve your email delivery rate for legitimate users. Email verification is especially powerful when combined with tools like the IP geolocation API and / or the phone number validation API to provide simple checks for new users.
Abstract's email verification API uses a variety of increasingly sophisticated and frequently updated techniques to ensure you suppress all invalid or risky emails. These techniques include (but are not limited to): checking for syntax errors and typos in the email address (e.g., john@gnamil.com), doing real time SMTP and MX record checks against the email's domain, performing a sophisticated regular expression (regex) check on the email, and using a variety of other filters backed by machine learning to detect invalid or risky emails.
We can also identify and flag other characteristics of an email, such as whether it's from a free email provider (such as Yahoo or Gmail), whether it's from a disposable email services (such as Yopmail), and whether it's from a 'role' email address (such as team@ or @sales@).
We can also help you identify emails that are from recently registered domains, even if those domains otherwise past other filters. Recently registered domains and emails can signal that the user is fraudulent, spammy, or in some other way needs to be reviewed.
February 26, 2021
-
Improved response time by 27%
February 16, 2021
-
Allow user to specify what fields and objects are included or not in the response using the "field" value in the request
February 12, 2021
-
Improve validations specific to Microsoft Office emails
November 20, 2020
-
Updated list of disposable and free email provides (+51)
August 14, 2020
-
Updated typos in docs and error handling for white spaces in submitted emails
August 12, 2020
-
Added 100+ new domains for disposable and free email services
July 2, 2020
-
Added 50+ new disposable email providers to the block list
June 10, 2020
-
Sped up MX and other domain checks to reduce overall response time by 25+ MS
Each of our API's has a free plan as well as several paid options, which offer a greater number of requests, a higher level of data quality, and greater speed for higher prices. Please see the page above or sign into your account to view pricing for each API.
Absolutely! We want you to try before you buy. Each of our API's has a free tier with a generous usage allowance for you to try the product out and verify that the speed and data quality work for you.
We use Stripe to accept payment via major debit and credit cards (Visa, Mastercard, American Express). If you cannot use those payment methods, then contact us at team at abstractapi.com to arrange for an alternative payment method.
Yes, you can upgrade or downgrade your subscription at any time by visiting your dashboard. If you upgrade in the middle of a billing cycle, you will be charged a pro-rated amount for your new plan through the end of the billing cycle.
Yes, all of our subscriptions are month to month. You can cancel at any time, and you will not be charged again at the end of your billing cycle.
You can cancel your subscription at any time from your dashboard. Once canceled, your subscription will be active until the end your current billing cycle, and then it will be automatically moved to the free plan.
If your API usage exceeds the monthly limit set by your plan, then you will be charged a fee for each call over your limit. At the end of your billing period, your usage will reset again.
We do offer enterprise plans with custom features and pricing in limited circumstances. If our public pricing plans don't work for you, then contact us (team at abstractapi.com) and we'll work something out.
While we don't normally offer discounts, we do make exceptions for certain types of users and use cases. If you are a student or are engaged in academic work, or are working on a non-profit or open source project, we're happy to offer you discounts for our API's. Just email us at team at abstractapi.com.
All of our plans are currently paid month to month. We will be launching annual plans at a discount soon. If you're interested in an annual plan in the meantime, just contact us and we'll set you up.
We will typically attempt to charge your payment method up to three times after it fails. If we're still unable to collect payment, then your subscription will be automatically canceled and you'll be moved to the free plan.
Yes, a paid tier of our API may be used in conjunction with a commercial project. The free tiers of our API's may not be used in commercial projects.
