Real-time API verification and bulk upload verification do the same underlying work: they confirm whether email addresses are deliverable. The difference is when and how you call the engine. The right choice depends on whether you are catching new addresses as they arrive or cleaning a stash you already have.
Real-time API: for the address arriving now
Use API verification when an address enters your system one at a time and you want a decision before completing the next step:
- Signup forms (block bad emails before account creation).
- Checkout pages (catch typos before sending receipts).
- Form submissions (lead capture, contact requests).
- CRM record creation (verify before sales sequence enrollment).
API responds in 1 to 2 seconds. The user experience supports a brief "checking..." state.
Bulk: for the list you already have
Use bulk verification when you have hundreds, thousands, or millions of addresses to check at once:
- Quarterly CRM cleanup.
- Pre-campaign list verification.
- Lead list cleaning before importing to a CRM.
- Annual newsletter list audit.
- Cold outreach prospect list preparation.
Bulk runs in the background, finishes in tens of minutes to a few hours depending on size, and gives you segmented CSV downloads.
The edges
Many addresses, but they need real-time decisions
If you have 10,000 leads from a webinar export and you want to push them into your CRM today with verification status, you have two options:
- Bulk upload, wait 30 minutes, import results.
- API loop with rate-limit handling, takes 3 hours.
Bulk wins on simplicity. Use API only if you specifically need per-address callbacks or live progress.
Few addresses, daily
If you have 100 new signups per day, API is the right pattern. Bulk has no benefit at this volume.
Many addresses, infrequently
Bulk every time. Even at 100,000 addresses, you submit once and the verifier handles parallelization.
Cost differences
For MailoClean, per-credit cost is identical between API and bulk. Both use the same credit wallet. The only difference is how you submit.
Other verifiers sometimes charge a premium for the API; check pricing carefully.
The hybrid pattern most teams use
- API at every entry point. Signup forms, checkout, lead capture all verify in real time.
- Bulk quarterly on the full CRM. Even with API at entry, lists decay. Quarterly bulk catches the decay.
- Bulk before any major campaign. Even a list verified last week benefits from one more pass before a high-stakes send.
FAQ
Do API and bulk use the same engine?
For MailoClean, yes. The same SMTP and DNS infrastructure powers both, so results are consistent.
Can I mix API and bulk in the same workflow?
Yes. Many teams do exactly this: API at the door, bulk for the back catalog.
Which is cheaper?
Same per-credit price. Bulk is sometimes slightly cheaper at the highest volume tiers due to bundle pricing.
Use both
API for arrivals, bulk for inventory. Read the API docs or upload a list now.