What an email validation API checks
An email validation API verifies an address programmatically, before you send to it. The checks run in layers: syntax, then whether the domain has a mail server behind it, then whether the mailbox actually exists and can receive.
Syntax. Is it shaped like an address at all. This is the only check most signup forms do, and it is nowhere near enough.
Domain and MX records. Does the domain exist, and does it have a mail server. Catches the classic typo: gmal.com instead of gmail.com.
Mailbox existence. Does the inbox actually exist and accept mail, checked without sending anything.
Disposable and role detection. Flags throwaway domains and role addresses like info@ that never convert and often complain.
Run in real time on a signup form, this blocks bots, catches typos while the user is still there, and keeps fake addresses out of your list from day one.
Why bounces wreck you
At my first email company we didn't clean our list properly. We assumed people would eventually engage. They didn't, and our sending performance paid for it. That mistake is why I have opinions about this now.
The industry average bounce rate is around 0.02 percent. Not 2 percent. When your bounces climb past that, mailbox providers read it as a signal you don't know your own list, and they start filing you under spam. I've watched a properly cleaned list drop a broken send from a 22.8 percent bounce rate to 0.20 percent. Same product, same copy. The only difference was validation before the send.
And validation is not a one-off. Every three months, remove the contacts who haven't opened or purchased in the last year. Unengaged addresses decay into dead ones, and dead ones bounce.
We police this on our own platform. I once flagged a two-day-old free account about to push 23,632 cold emails through a fresh sending reputation. That send would have burned the domain before the account was a week old. Validation and warmup are not compliance theatre. They are the difference between a sending reputation and a smoking crater.
The platform enforces it for you too: cross a 2 percent bounce rate and sending auto-pauses while we look at what happened. The threshold is smarter than a bare percentage, because two dead addresses in a 57-send campaign is noise, not a crisis. The pause only fires when the rate breach comes with a minimum absolute count of bounces behind it.
Where validation belongs
Most of the industry sells validation as a separate list-cleaning product. You export your list, upload it to a verifier, pay per thousand, download the results, and import them back. Every quarter, forever.
Verification should live inside your contacts, where the send already happens. In Nitrosend it is part of contact enrichment: enrich a contact and the verification status lands in the same table you send from, with NeverBounce doing the checking under the hood. One call, no export loop.
curl -X POST https://api.nitrosend.com/v1/my/contacts/{id}/enrich \ -H "Authorization: Bearer $NITROSEND_API_KEY" → { "verification_status": "valid" }