How do I use the Valid Email Checker API alongside double opt-in?

Real-time verification and double opt-in (DOI) catch overlapping but not identical problems. Real-time catches typos and disposables at the form. DOI confirms intent and address ownership through a click. Running both is the gold standard for high-stakes signup flows — regulated industries, court-defensible consent, large-volume marketing. Here's how to layer them cleanly in a Valid Email Checker setup.

The two-layer flow

1. User submits the signup form. Your backend calls verify-single with the address.
2. Real-time decision. If status is invalid, disabled, disposable, or spamtrap, reject the form with a clear error message and ask the user to retype. Do not send a confirmation email — sending to a confirmed-bad address risks the message being a spam-trap hit.
3. Address passed verification. Status is safe, risky, catch_all, role, inbox_full, or unknown. Continue to step 4.
4. Send the DOI confirmation email. Mark the subscriber as pending in your database. Send the confirmation message with a link containing a one-time token.
5. User clicks the link. Flip the subscriber from pending to active. They are on the list.
6. User does not click within a window (typically 24 to 72 hours). The pending row expires and the address never makes it to the active list.

Why this beats DOI alone

DOI on its own does not stop someone from typing info@theircompany.com or john@gmial.com on the form. The confirmation email goes to a typo'd address that bounces, or to a role inbox where the team owner did not consent. Real-time verification catches both before the confirmation step even happens. Your sender reputation never takes the hit of bouncing a confirmation email to a typo.

Why this beats real-time alone

Real-time verification proves the address exists. It does not prove the human at the form actually owns the address. For consent-critical flows (GDPR-strict markets, transactional consent for regulated industries) you still need the click. The combined approach gets both signals on every signup.

Cost math

Each form submit costs:

• 1 Valid Email Checker credit on the verification call (Unknown is auto-refunded, so 1-3% of calls are effectively free).
• 1 transactional email send through your ESP for the confirmation message.
• 0 extra cost on the click — your backend handles it.

Roughly: a Valid Email Checker call is well under a cent per address; an ESP transactional send is cheap. The combined per-signup cost is barely material for any real business.

When this is overkill

Skip the two-layer flow if your signup is gated by something stronger than email (SSO, paid checkout, in-person event registration). The external trust signal does the work that DOI would do, and real-time verification at the form is enough on top.