Integration guide Use case

Email Validation API for Developers

Check addresses before creating accounts or processing an email list. Make an authenticated request from your backend, then apply the validation signals to your own acceptance rules.

Make your first verification request

Create an account and get an API key. Keep the key on your server; do not embed it in browser JavaScript. URL-encode the email address when building the request path.

curl --request GET \
  --header "Authorization: Bearer YOUR_API_KEY" \
  --header "Accept: application/json" \
  "https://easyemailapi.com/api/verify/tim%40apple.com"

Tim at Apple is a fictional example; replace the address with one you control when trying the API. The endpoint verifies one address per request. See the API documentation for more integration details.

Read the response before deciding what to accept

  • valid: the validation result. It does not establish that the user owns the address.
  • valid_mx and mx: mail-routing signals for the domain, not proof of an individual mailbox.
  • disposable: a recognized disposable email provider. Use it to enforce your signup policy.
  • free_email: a recognized free provider. A free address can belong to a legitimate customer.
  • user, domain, tld, and sub: parsed components and plus-addressing information.
  • score and max_score: interpret together; available checks affect the maximum score.
  • inbox_check_enabled: whether SMTP checks were enabled for this result. Pro enables these checks.
  • inbox_exists and catch_all: SMTP signals. False values do not establish that a mailbox is missing or that a domain is not catch-all: checks may be disabled, skipped, or interrupted. On a catch-all server, individual inbox existence remains unconfirmed.

Validate signup emails on your backend

  1. Check that the form contains an email address, then call the API from your server with a timeout.
  2. Ask users to correct invalid addresses. Apply your disposable-provider policy separately from free-provider detection.
  3. Handle unavailable or inconclusive checks according to your product's needs: allow a confirmation-email flow or offer a retry.
  4. Send a confirmation email to verify ownership. Verification cannot guarantee delivery or inbox placement.

Read more about signup form validation and catch-all email decisions.

Handle API errors and usage limits

The free plan allows 5,000 checks per month at 30 requests per minute. Pro allows 100,000 monthly checks at 120 requests per minute.

  • 401: check your bearer token. Retrying an invalid key will not fix authentication.
  • 403: the monthly verification limit has been reached. Review usage or upgrade your plan.
  • 429: slow down requests and respect the Retry-After header before retrying.
  • Network errors or server errors: use bounded retries with backoff. Do not treat a failed request as an invalid email address.

For lists, queue work within your plan's rate limit or use the Pro email-list cleanup tool.

Start with the checks your workflow needs

Explore the free email verification API, review plans and pricing, or get your free API key.