MailForge MailForge

MailForge API

Real‑time email validation and deliverability intelligence.

⚡ Low-latency
🔐 Privacy-first
🛡️ Disposable detection
🧠 Typo suggestions

Who it's for

What it does

MailForge validates emails in real time by combining syntax, MX, and SMTP checks, plus disposable and role‑based detection and smart typo suggestions. It also maintains continuously updated Allow and Block lists to improve accuracy and reduce false positives.

⚡ Real‑time
Low‑latency responses.
🧠 Accuracy
MX+SMTP+heuristics with domain corrections.
🔒 Privacy‑first
No email storage; GDPR by design.
🪄 Smart lists
Auto‑updated allow/block lists for trusted & risky domains.

Tip: set "deep": true to enable SMTP-level mailbox verification (more accurate); omit or set false for faster syntax+MX only.

Use cases

1) Sign-up & Login

Validate before creating accounts; block disposable and suggest corrections.

POST /v1/validate
{
  "email": "user@gmial.com",
  "timeout_ms": 4000,
  "deep": true
}
→ { "status": "invalid", "suggestion": "user@gmail.com", "reason": "typo" }

2) Marketing forms

Integrate in lead forms to lower bounces and protect sender score.

if (v.status === "valid" && !v.disposable && v.mx.has_mx) acceptLead()

3) Database cleansing

Batch/bulk to sanitize lists before campaigns.

POST /v1/bulk {
  "emails": ["a@x.com","b@y.com"],
  "timeout_ms": 4000,
  "deep": true
}

4) Anti-abuse & Trials

Block trials with temporary or role-based emails (admin@, info@).

if (v.role_account || v.disposable) denyTrial()

5) Transactional email pre-check

Validate before sending password resets, invoices, or 2FA codes.

if (!v.smtp.accepts_mail) queueRetry(email)

6) Third-party imports

Auto-validate emails imported from CSVs, partners, or forms.

for (const e of emails) {
  const v = await validate(e);
  if (v.status !== "valid") flag(e);
}

7) Domain monitoring

Detect expired/misconfigured MX to catch deliverability risk early.

if (!v.mx.has_mx) alertTeam(v.email)

8) Scoring & lead qualification

Use the score and risk flags to prioritize outreach.

if (v.score < 0.8 || v.disposable) markAsLowQuality(email)

Performance & Security

Performance

  • • Low-latency API responses
  • • Autoscaling under load
  • • Configurable timeouts

Security

  • • HTTPS-only
  • • Token-based auth / marketplace headers
  • • Strict CORS

Privacy

  • • No email storage
  • • GDPR-friendly by design
  • • Minimal logs

Errors & status codes

StatusWhenBody (example)
200Validation succeeded{"status":"valid"}
400Invalid input{"error":"bad_request","message":"email is required"}
401Missing/invalid auth{"error":"unauthorized"}
429Rate limited{"error":"rate_limited","retry_after":30}
5xxUpstream error{"error":"server_error"}

See API Docs for full schema.

FAQ

Do you store emails?

No. MailForge does not store email addresses; results are computed on the fly.

How do I authenticate?

Use Authorization: Bearer YOUR_API_KEY for direct/Stripe plans. Some marketplaces (e.g., RapidAPI) require their own header.

Rate limits?

Per-plan rate limits apply. See Docs for details.

Is there a sandbox?

Yes, MailForge provides a fully isolated sandbox environment that runs in scale-to-zero mode. This means that the sandbox consumes no resources when idle and automatically spins up on the first request.
It follows our Sustainability & Efficiency principles, optimizing energy usage while maintaining real-world accuracy for integration tests.

You can request a 48-hour trial of the sandbox for extended testing or evaluation. Contact us to activate your temporary access.

Developer docs

Endpoints: /v1/validate (single), /v1/bulk (batch), /v1/health (status).

View API Docs