ValidatedMails.com

Email verification API

ValidatedMails gives developers a real-time API for verifying email addresses before accounts, leads, forms, and outbound sends depend on them.

Real-time checks for production workflows

Call the API when a user signs up, when a lead enters your system, or when an outbound workflow needs a fast deliverability decision.

  • Syntax and normalization
  • Domain and MX availability
  • Disposable and role account detection
  • Accept-all and risky mailbox signals

Built for engineering teams

The API returns structured status, score, reason, and signal fields so your application can route valid, risky, invalid, and unknown outcomes intentionally.

  • JSON responses
  • GET and POST examples
  • Language guides for Python, JavaScript, Go, Java, C#, PHP, and Rust
  • Clear API response reference

When to use it

Use the API anywhere a bad email address creates cost, fraud, support load, or failed communication.

  • Signup validation
  • Lead enrichment
  • Checkout and account creation
  • Sales and marketing automation

FAQ

What does the email verification API return?

The API returns structured verification data rather than only a boolean. Typical consumers use status, score, reason, normalized email, domain, MX hosts, disposable, role, accept-all, and related signals to drive product or operations policy.

Where should the API be called in a production system?

Common integration points include signup forms, lead capture, CRM imports, outbound campaign preparation, account recovery flows, and enrichment pipelines. The right placement depends on whether the system needs to block bad addresses immediately or mark them for review downstream.

Is email verification deterministic?

Some checks are deterministic, such as syntax and many DNS failures. Mailbox-oriented checks can be probabilistic because mail providers may use catch-all routing, greylisting, temporary deferrals, or anti-abuse behavior. The API exposes reason and risk fields so callers can handle uncertainty explicitly.

Does the API check MX records?

Yes. MX and DNS data are part of the verification process and help distinguish malformed addresses, domains without mail routing, and domains that require mailbox-level policy handling.

Does the API detect disposable and role addresses?

Yes. Disposable and role-account signals are returned separately so application teams can decide whether to reject, allow, throttle, or review those addresses based on their own product policy.

How should engineering teams use risky or unknown results?

Risky or unknown results should normally be routed to a product-specific policy instead of treated as hard failures. Examples include confirmation emails, manual review, lower sending priority, or delayed retry depending on the workflow.

Do API credits expire?

No. Credits do not expire, and API checks use the same shared credit balance as single validation and bulk validation workflows.