Verify Email Address API

This email checker API allows you to validate an email address. The validation will parse the name if possible and check whether the email is not just a disposable junk email address. The API will also check if the email is from a free provider like Gmail, Yahoo, or Hotmail.

Additionally, if the owner of the address has a public Gravatar profile, you get their name and avatar. This can be useful for user registration forms to show the user a preview of their profile picture.

Response fields

  • result: valid when the mail server confirmed the mailbox; invalid when it rejected it or the domain cannot receive mail from the internet (it does not exist, has no MX record or a null MX, is an internal name such as localhost or .internal, or its mail servers resolve only to private, loopback or link-local addresses; these are decided from DNS and no mail server is contacted); unknown when the mailbox cannot be confirmed: on a catch-all domain (accept_all is true) or when the mail server did not answer within about 7 seconds and there is no earlier answer for that address. Results are cached per address for up to 30 days (1 day for unknown, 1 hour when the mail server did not answer).
  • first_name, middle_name, last_name, full_name: from the public Gravatar profile of that exact address or, if it has none, parsed from the address itself ([email protected] gives Max Test, [email protected] John Michael Smith, [email protected] Jean-Luc Picard). A name written all in lower case, as parsed from the address, gets a capital letter on every part; a name with capitals keeps the casing its owner typed on Gravatar (Van der Berg). Initials are not names: [email protected] gives only the last name Smith. We never look names up anywhere else, so a part that cannot be derived is null. full_name joins the known parts.
  • username: always the part before the @.
  • image: the Gravatar avatar registered for that exact address, or null if there is none. Gravatar's default picture is never returned.
  • disposable: whether the address is from a disposable (throwaway) provider, from the verification and our own list (the community disposable-email-domains list plus our additions, minus real mail providers it lists by mistake).
  • free_provider: whether the address is at a free provider where people keep a permanent mailbox (Gmail, Yahoo, Outlook). Never true for a disposable address.
  • accept_all: whether the domain's mail server accepted an address that cannot exist (a catch-all domain). Many company domains behind Google Workspace, Microsoft 365 or a mail security gateway answer this way. It is false when the server rejected the test, blocked it or did not answer.

Input, errors and limits

Send one address of at most 320 characters (64 before the @), URL-encoded (a + as %2B). A missing, empty, repeated or malformed email parameter returns HTTP 400 and is not billed; an address with a space gets a 400 that says to send + as %2B, since an unencoded + arrives as a space. Every error has the same JSON body, for example {"status": "failure", "code": 400, "message": "Please provide an email address."}. Each API key can run a fixed number of requests at the same time, set by its plan; more parallel requests get HTTP 429 with the message Too many concurrent requests. An answer usually takes about a second; a mail server that does not answer within about 7 seconds makes result unknown.

Based on the verification result, you can decide whether to allow the user to register with the email address or block it because of invalid temporary email addresses or free email providers if you are only interested in business users.

Make sure to read about the best email APIs to supplement your app.

GET
https://api.apileague.com/verify-email
Example Request and Response
GET
https://api.apileague.com/{{ examples.getVerifyEmail }}
{
  "email": "[email protected]",
  "domain": "gmail.com",
  "first_name": null,
  "middle_name": null,
  "last_name": null,
  "full_name": null,
  "username": "maxtest",
  "image": null,
  "result": "valid",
  "disposable": false,
  "accept_all": false,
  "free_provider": true
}
cURL
Java
Javascript
Python
Go
C#
 {{ codeCopyText }}
 {{ codeCopyText }}
 {{ codeCopyText }}
 {{ codeCopyText }}
 {{ codeCopyText }}
 {{ codeCopyText }}

Frequently Asked Questions

What does the email verification check for?

The API checks if the email format is valid, if the domain exists, if it's a disposable or free email provider, and attempts to verify if the mailbox exists.

Can it detect disposable email addresses?

Yes, the API specifically checks against a list of known disposable email providers to help you prevent spam and fake registrations.

Does it send an actual email to the user?

No, the verification process is done without sending an actual email to the user, so it is non-intrusive.

Why is the result unknown for some addresses?

Some domains are catch-all: their mail server accepts mail for any address, so no single mailbox can be confirmed. For those, accept_all is true and result is unknown. Result is also unknown when the mail server does not answer.

How is the Email Verification API different from the Extract Authors API?

The Email Verification API validates email addresses and checks for deliverability, while the Extract Authors API finds author names from news articles or web pages.

Questions? Need Help? Ask Away