Free Email Verification API: Real-Time Validation with Code Examples

Every signup form, CRM import, and cold email sequence creates the same problem: addresses that look valid can still bounce, and bounces destroy sender reputation fast. Adding real-time email validation at the point of entry stops bad addresses before they reach your sending queue. Our free email validator lets you test any address in the browser, and the email verification API plugs directly into your application so you can validate programmatically at scale.

This guide walks through what a solid email verification API returns, how to call it with real code examples, and which use cases make the most of real-time validation.

What a Good Email Verification API Returns

A minimal API call returns a status string. A useful one returns structured data your application can act on without additional logic. Here is what a complete response looks like from the StartupHub API (/api/v1/email/validate):

{
  "email": "[email protected]",
  "status": "valid",
  "deliverable": true,
  "score": 94,
  "mx_found": true,
  "mx_record": "mail.acmecorp.com",
  "disposable": false,
  "catch_all": false,
  "format_valid": true,
  "domain": "acmecorp.com"
}

The status field carries one of four values: valid (safe to send), invalid (mailbox does not exist or domain has no MX record), catch-all (server accepts everything, result inconclusive), or risky (disposable or known-bad pattern). The score is a 0-100 deliverability confidence number. Your application can use it to set thresholds rather than treating every address as binary pass/fail.

Making Your First API Call

The validation endpoint accepts a GET request with the address as a query parameter. Authenticate with your API key in the Authorization header. You can get an API key at no cost at the API docs page; the free tier covers 50 validations per day.

JavaScript (fetch)

const response = await fetch(
  'https://www.startuphub.ai/api/v1/email/validate?email=jane.smith%40acmecorp.com',
  { headers: { Authorization: 'Bearer YOUR_API_KEY' } }
);
const result = await response.json();

if (result.status === 'valid') {
  // safe to proceed
} else if (result.catch_all) {
  // inconclusive: flag for manual review
} else {
  // block or prompt user to re-enter
}

Python (requests)

import requests

resp = requests.get(
    'https://www.startuphub.ai/api/v1/email/validate',
    params={'email': '[email protected]'},
    headers={'Authorization': 'Bearer YOUR_API_KEY'}
)
data = resp.json()
print(data['status'], data['score'])

cURL

curl -s \
  "https://www.startuphub.ai/api/v1/email/[email protected]" \
  -H "Authorization: Bearer YOUR_API_KEY"

Email Discovery: Find a Work Address by Name and Domain

The discovery endpoint (/api/v1/email/discover) finds a person's most likely work email from their first name, last name, and company domain. It checks the domain's known email format patterns and returns validated candidates.

curl -s \
  "https://www.startuphub.ai/api/v1/email/discover?first_name=Jane&last_name=Smith&domain=acmecorp.com" \
  -H "Authorization: Bearer YOUR_API_KEY"

The response includes the discovered address, its validation status, and a confidence score. Free tier: 5 discoveries per day. For higher volume, see the paid plans at the API docs.

Where to Add Email Validation in Your Stack

Signup and lead capture forms

Call the validation endpoint on blur (when the user leaves the email field) or on form submit. A sub-200ms API response is fast enough to validate before the form completes. If the status is invalid, prompt the user to re-enter immediately, before the address ever reaches your database or CRM. This is the highest-leverage integration point: it prevents bad data at the source.

CRM and list imports

When a CSV lands in your CRM or marketing platform, run each address through the API before the import commits. A simple script reads from the file, calls the API per row, and writes a validation_status column back. Filter out invalid rows before import. This step typically removes 10 to 20 percent of addresses from purchased or scraped lists and reduces bounce rates to under 1 percent on the first send.

Cold email sequences

Outbound teams often discover emails from multiple sources (domain search, LinkedIn enrichment, manual research). Validate every discovered address before it enters a sequence. Valid addresses go straight into the queue. Catch-all addresses can be manually reviewed. Invalid addresses get dropped. This keeps your sending domain off blocklists without changing the rest of your outreach workflow.

Webhook and ingest pipelines

If your backend receives email addresses via webhook (Stripe billing updates, form submissions, API callbacks), add a validation call in the ingest handler. Store the validation result alongside the address. This lets you segment unvalidated or risky addresses in your marketing platform without blocking the ingest flow.

The Email Intelligence Market: Where APIs Fit

StartupHub.ai data shows the email intelligence and sales prospecting market is increasingly API-first. Across the five email finder and verification platforms we track closely, including Lusha (StartupHub score 72), Cognism (65), Apollo.io (64), Snov.io (50), and Findemail (25), every platform now exposes a developer API as a core product feature. The category has moved beyond browser-only tools toward infrastructure that embeds directly into sales stacks and product workflows.

Free vs. Paid Email Verification APIs: What You Get

Free tier (StartupHub API)

50 validations per day, 5 discoveries per day, no credit card required. The free tier is designed for individual developers evaluating the API, building a side project, or validating at low volume. JSON responses include all fields: status, score, mx_found, disposable, catch_all.

NeverBounce API

NeverBounce offers a pay-as-you-go API starting at $8 per 1,000 verifications (July 2026). It does not include email discovery. Its API is well-documented, widely integrated with CRM platforms, and suited for teams that need high-volume bulk validation. No free tier for the API itself; new accounts receive 1,000 free credits via the dashboard.

ZeroBounce API

ZeroBounce bundles validation with supplementary data: email scoring, activity data, geographic information, and gender detection. Its API includes a free tier of 100 validations per month. Paid pricing runs roughly $1.50 per 1,000 at 100,000+ volume. Its strength is enrichment on top of validation; its weakness is cost at low and mid volumes compared to point-solution alternatives.

Hunter.io API

Hunter.io's API combines email finding (domain search, name-based discovery) and verification using a shared credit pool. One credit finds; 0.5 credits verify. The free tier provides 25 monthly API calls across both endpoints. Paid plans start at 34 euros/month for 500 credits. Best fit: teams that need both finding and verification in one API and are already on the Hunter.io dashboard.

Frequently Asked Questions

What is an email verification API?

An email verification API is an HTTP endpoint that accepts an email address and returns its deliverability status. A full-featured API checks syntax, DNS MX records, and the recipient mail server response to confirm whether the specific mailbox exists. It returns structured data (typically JSON) that your application can act on in real time.

How do I get a free email verification API key?

Visit StartupHub's API docs, create a free account, and copy your API key from the dashboard. The free tier includes 50 validations and 5 email discoveries per day at no cost, with no credit card required.

Can the API validate email addresses in bulk?

Yes. The /api/v1/email/validate endpoint is designed for programmatic use and can be called in a loop or with concurrent requests. For large batches (tens of thousands of addresses), coordinate your request rate with the API's rate limits. The API docs include rate limit details and a bulk validation guide.

What does "catch-all" mean in API results?

A catch-all domain is configured to accept delivery for any address at that domain, even addresses that do not correspond to real inboxes. When the API returns catch_all: true, the SMTP step could not determine whether the specific mailbox exists, because the server accepts everything. These results require a judgment call rather than a hard accept/reject decision.

How accurate is real-time email verification?

For domains that respond normally to SMTP probing, accuracy is high: the verification handshake either confirms or denies the mailbox. Accuracy drops for catch-all domains, which are designed to be inconclusive, and for mail servers that have rate-limited or blocked verification probes. A deliverability score in the API response reflects this uncertainty.

Should I validate emails on the frontend or backend?

Validate on both. A lightweight syntax check on the frontend gives immediate feedback. The API call belongs on the backend: it keeps your API key out of client-side code, prevents users from bypassing validation via browser tools, and keeps your rate limit usage clean. The response can be returned to the frontend as part of the form submission flow without adding perceptible latency.

What is the difference between email validation and email verification?

Email validation usually refers to format checking: confirming the address follows the correct pattern ([email protected]). Email verification goes further: it checks that the domain has MX records, connects to the mail server, and confirms the mailbox exists. The terms are often used interchangeably, but verification is the more complete and accurate process. The StartupHub API runs the full verification stack, not just format validation.