Why Validate Emails at the Point of Entry?
Every invalid email that enters your database costs you money — from wasted ESP credits to damaged sender reputation. For SaaS companies, the signup form is where data quality either starts strong or begins to degrade.
Real-time API validation checks each email address as the user enters it, before they complete signup. Bad addresses never make it into your system. The result: cleaner lists, fewer bounces, and higher-quality signups from day one.
Real-Time Validation Flow
How API validation works in your signup form
User enters email
On signup form
API validates instantly
< 3 seconds
Result returned
Valid / Invalid / Risky
Form responds
Accept or show error
What Real-Time Validation Catches
A single API call checks the email against multiple validation layers in under 3 seconds:
- Syntax errors — Misformatted addresses like
[email protected]oruser@@company.com - Invalid domains — Domains that don't exist or have no MX records
- Disposable emails — Temporary addresses from services like Mailinator, Guerrilla Mail, TempMail
- Spam traps — Known honeypot addresses that damage sender reputation
- Catch-all domains — Servers that accept all emails (flagged for special handling)
- Role-based addresses — Generic addresses like
info@,admin@,support@
EmailVer API Overview
EmailVer provides two types of API to fit different use cases:
Real-Time Verification API
For single email checks — signup forms, login flows, lead capture, CRM integrations. Send one email, get an instant response with the full verification result.
// Real-time email verification
GET /api/v1/verify?email=[email protected]
// Response
{
"email": "[email protected]",
"status": "valid",
"score": 98.5,
"disposable": false,
"catch_all": false
}
Bulk Verification API
For verifying entire lists programmatically. Upload a list via API, get results back without manually importing/exporting from the dashboard. Ideal for automated data pipelines and scheduled list cleaning.
API Response Explained
Every verification call returns a detailed response with multiple data points you can use to make decisions:
API Response Fields
What you get back from every verification call
emailThe email address checked
statusvalid | invalid | catch_all | unknown
scoreDeliverability confidence score (0–100)
disposableIs it a temporary/throwaway address?
catch_allDoes the domain accept all emails?
mx_foundDoes the domain have valid MX records?
smtp_checkDid the mailbox respond to SMTP ping?
Integration Guide: Step by Step
Step 1: Get Your API Key
Sign up at EmailVer and grab your API key from the dashboard. You get free credits to test the integration before committing.
Step 2: Add Validation to Your Signup Form
The simplest approach is to validate on form submission, before creating the user account. Here's a basic implementation:
// Validate on form submit
async function validateEmail(email) {
const res = await fetch(
`https://api.emailver.com/v1/verify?email=${email}`,
{ headers: { "Authorization": `Bearer ${API_KEY}` } }
);
const data = await res.json();
if (data.status === "invalid") {
showError("Please enter a valid email");
}
}
Step 3: Handle Different Statuses
Don't just check for valid/invalid — handle each status appropriately:
- Valid — Allow signup immediately
- Invalid — Show an error message and ask the user to re-enter
- Disposable — Block signup or flag the account for review
- Catch-all — Allow signup but flag for monitoring (see our catch-all guide)
- Unknown — Allow signup but add to a verification watchlist
Step 4: Add Inline Feedback
For the best user experience, validate on field blur (when the user tabs away from the email input) rather than on form submit. Show a green checkmark for valid addresses and a helpful error message for invalid ones. This reduces form abandonment by catching issues early.
Best Practices for API Integration
Don't Block on Network Failures
If the API is unreachable (network timeout, service issue), don't block the signup. Fall back to basic client-side validation and flag the address for async verification later. Never let an external API become a single point of failure for your signup flow.
Cache Results Intelligently
If the same email is submitted multiple times (e.g. user retries after a different form error), don't call the API again. Cache results for the duration of the session. This reduces API calls and speeds up the user experience.
Rate Limit Abuse Protection
Bad actors can abuse your form to enumerate valid email addresses or burn through your API credits. Add rate limiting to your validation endpoint — no more than 5–10 validation requests per IP per minute is a reasonable default.
Log Everything
Track validation results in your analytics. Monitor what percentage of signups are invalid, disposable, or catch-all. This data helps you identify signup form abuse and measure the ROI of API validation.
Common Use Cases Beyond Signups
- Lead capture forms — Validate before adding contacts to your CRM or marketing automation
- Checkout flows — Ensure order confirmation emails will be delivered
- Contact forms — Reduce spam submissions from bots using fake addresses
- CRM data imports — Validate via bulk API when importing contact lists from other systems
- User profile updates — Re-validate when users change their email address
ROI of Real-Time Validation
The numbers make a compelling case for API validation:
- Fake signup reduction: 60–80% fewer fake or disposable email signups
- Bounce rate improvement: Near-zero hard bounces from new signups
- ESP cost savings: Stop paying to send emails that will never be delivered
- Support ticket reduction: Fewer "I didn't receive my confirmation email" tickets
- Data quality: Every email in your database is verified from the start
Final Thoughts
Real-time email validation is one of the highest-ROI integrations a SaaS company can make. It takes a few hours to implement and immediately improves data quality, deliverability, and user experience.
Get your free EmailVer API key and start validating emails at the point of entry — before bad data ever touches your database.