See it in Action!
There’s plenty of significant reasons behind having proper validation in place:
- Sending emails to fake/no-longer-existent addresses will hurt your deliverability.
- Mistyping an email address will block users from confirming their account or resetting a password.
- Valid e-mail addresses, lets you stay in touch with users.
curl --location --request GET 'https://api.apilayer.com/email_verification/cust[email protected]' \ --header 'apikey: YOUR API KEY HERE'
Yes!. so simple. :) Check the documentation tab for more information.
How it works
This API is the one and the only solid solution to verify that the e-mail address is valid, and reachable. We achieve this functionality by validation with regex, validating the DNS for MX records and than connecting the recipient's SMTP server for validation, without sending any email.
Yes! this email verification API actually connects to the mail server and checks in real-time if the email exists. We don't use historical data.This is the most robust and solid way that is possible within the SMTP protocol's limitations.
What information is provided with the API?
A sample response from the API is here:
is_disposable: Checks if the e-mail is from a disposable e-mail provider such as mailinator.com.
is_catch_all: A catch-all address is meant to catch all email sent to any non-existing email accounts on your domain.
is_inbox_full: If the remote user's inbox is full, this may be the reason for bounced e-mails.
is_disabled: Tells us if the remote account is disabled and unable to accept the e-mail you've sent.