Every signup form needs the same two checks: is this email real, and is this phone number real? Yet...
Every signup form needs the same two checks: is this email real, and is this phone number real? Yet the API market makes you buy them separately - one vendor for email verification, another for phone lookup, two subscriptions, two SDKs.
I built Contact Validation API to do both in one call, with a free tier that covers most side projects (500 requests/month, no card).
What it checks
Email - one GET request returns:
{
I kept needing the same small checks in side projects — is this email real, is this phone number...
We just shipped two new endpoints on Validate, the validation/utility API — both format-only checks,...
Bad email addresses in a signup form don't just clutter your database, they wreck deliverability. A...
A backend-focused pattern for testing REST API verification emails with isolated inboxes, cleaner assertions, and less…
The pattern /.+@.+\..+/ accepts admin@mailinator.com, test@defunct-domain.io, and notreal@typo.vom....
"Email verification" sounds like one thing, but it's really a stack of checks of increasing depth and...
