Email

4 endpoints for email deliverability: verification, SPF / DKIM / DMARC posture, contact extraction, format parsing.

For outbound sales, ESP integrators, fraud and onboarding teams.

Endpoints in this bundle

Each endpoint is independently callable. Bundle membership is for discovery only — you do not need to opt in.

Method	Path	Credits	Summary
POST	/v1/verify/email	1	Syntactic, MX, and disposable-domain detection.
POST	/v1/intel/email-auth	1	SPF, DKIM, and DMARC posture for a domain.
POST	/v1/extract/contacts	1	Pull emails, phones, and socials from a page.
POST	/v1/parse/email	1	Parse an address into local-part, domain, plus-tag, and display-name.

Recipe

List hygiene before send

Parse each address with /v1/parse/email to normalize and strip plus-tags before deduplication.
Call /v1/verify/email on the deduped list to drop syntactic failures, MX-less domains, and disposable providers.
For surviving addresses, call /v1/intel/email-auth on the domain to flag any sending domains with no DMARC alignment — those are higher bounce risk.

Sample code

Try a request

Pick a language. Click to expand the snippet.

curl

curl -X POST https://api.ollagraph.com/v1/verify/email \
  -H "Authorization: Bearer $OLLAGRAPH_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"email":"[email protected]"}'

python

import httpx, os

r = httpx.post(
    "https://api.ollagraph.com/v1/verify/email",
    headers={"Authorization": f"Bearer {os.environ['OLLAGRAPH_API_KEY']}"},
    json={"email": "[email protected]"},
    timeout=15.0,
)
print(r.json())

node

const res = await fetch("https://api.ollagraph.com/v1/verify/email", {
  method: "POST",
  headers: {
    "Authorization": `Bearer ${process.env.OLLAGRAPH_API_KEY}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({ email: "[email protected]" }),
});
console.log(await res.json());

FAQ

Email bundle FAQ

Do you do SMTP RCPT-TO probing?

No. We stop at syntactic checks, MX resolution, and disposable-domain matching. SMTP probes get IPs blacklisted and producers false-negatives on greylisting servers.

Will you flag @ollagraph.com or @qcrawl.com as nonexistent?

No — both are catch-all domains in our knowledge base. They always validate as deliverable at the MX level.

Why does email-auth sometimes return DMARC `policy=none`?

That is the published policy at the domain. We report what the DNS says; we do not infer intent.

Email

Endpoints in this bundle

List hygiene before send

Try a request

Email bundle FAQ

Ship with the Email bundle.