Compare two emails
API · /emailnormalize-api
Email Normalize API
healthy
3,885 Subscribers
Canonicalize email addresses so you can deduplicate accounts and catch different aliases of the same inbox. The normalize endpoint lower-cases the address and applies provider-aware rules: it strips the dots from Gmail and Googlemail local parts (because Gmail ignores them) and maps googlemail.com to gmail.com, removes +tag sub-addressing for Gmail and the many providers that support it — Outlook, Hotmail, Live, iCloud, Fastmail, Proton, Yandex, Zoho, GMX and more — and, by default, for every domain so duplicates never slip through, while reporting exactly which changes it made and which provider it detected. The compare endpoint normalizes two addresses and tells you whether they resolve to the same mailbox. Everything is computed locally and deterministically, with no DNS or network calls, so it is instant and private. Ideal for sign-up and registration dedup, fraud and abuse prevention (one person, many aliases), CRM and mailing-list hygiene, and merging customer records. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This normalizes addresses for comparison; to verify that an address actually exists and can receive mail (MX, disposable, role accounts) use an email-verification API.
api.oanor.com/emailnormalize-api
API health
healthy- Uptime
- 100.00%
- Server probes · 24h
- Avg latency
- 88 ms
- Server probes · 24h
- Subscribers
- 3,885
- active
- Total calls
- 36
- last 7 days
Pricing
Pick a tier — billed monthly, cancel anytime.
Free
Free
- 3,935 calls / month
- 2 requests / second
- Hard cap (429 above quota, no overage)
- 3,935 calls/month
- 2 req/sec
- Normalize + compare
- No credit card
Starter
€5.45 /month
- 13,450 calls / month
- 8 requests / second
- Hard cap (429 above quota, no overage)
- 13.45k calls/month
- 8 req/sec
- Provider-aware + plus-tags
- Email support
Pro
€25.35 /month
- 185,500 calls / month
- 20 requests / second
- Hard cap (429 above quota, no overage)
- 185.5k calls/month
- 20 req/sec
- Sign-up dedup / anti-fraud pipelines
- Priority support
Mega
€63.35 /month
- 970,000 calls / month
- 50 requests / second
- Hard cap (429 above quota, no overage)
- 970k calls/month
- 50 req/sec
- Platform scale
- Dedicated SLA
Built by
Related APIs
Other APIs with overlapping tags.
MIME Encoding API
The email and MIME text encodings that general base64/hex toolkits leave out. The quoted-printable endpoint encodes and decodes Quoted-Printable (RFC 2045) — the Content-Transfer-Encoding that keeps mostly-ASCII text readable while escaping everything else as =XX hex, with the soft line-wrapping at 76 columns and trailing-whitespace handling the spec requires. The encoded-word endpoint encodes and decodes RFC 2047 encoded-words — the =?UTF-8?Q?…?= and =?UTF-8?B?…?= form used to carry non-ASCII text in email Subject, From, To and other headers — in either the Q (quoted-printable-style) or B (base64) variant, and decodes any mix of them back to plain text. Everything is UTF-8 and computed locally and deterministically, so it is instant and private. Ideal for building and parsing email (SMTP/IMAP), .eml and MIME tooling, newsletter and transactional-mail systems, and migrating legacy mail data. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. These are the MIME-specific encodings; for base64, base32, hex, URL and HTML entity encoding use a general encoding API.
api.oanor.com/mimeencode-api
Template API
Render templates with your data. Pass a Handlebars or Mustache template plus a JSON data object and get back the rendered text — ideal for dynamic emails, SMS and notifications, document and report generation, code scaffolding, and any "fill in the blanks" output. Handlebars supports blocks like {{#each}} and {{#if}} and is HTML-escaped by default (turn off with escape=false); Mustache is logic-less with sections and inverted sections. Both engines are safe — there is no arbitrary code execution. Pure local rendering — no key, no third-party service, instant. Live. 3 endpoints. Distinct from a Markdown renderer or a fake-data generator.
api.oanor.com/template-api
Email Parser API
Parse a raw email (RFC 822 / MIME / .eml) into clean, structured data. Send the raw message (or a URL to a .eml file) and get back the sender, recipients (to / cc / bcc / reply-to) with names and addresses split out, the subject, the parsed date, the Message-ID, In-Reply-To and References (for threading), priority, the plain-text and HTML bodies, every header, and metadata for each attachment (filename, content type, size, content-id — never the binary payload). A /v1/headers endpoint returns just the header map. Parsing is fully local (no third-party service) and nothing is stored. Live. 3 endpoints. Built for inbound-email processing, .eml viewers, mailbox import, ticketing and email-automation pipelines. Distinct from address validation and SPF/DMARC checks.
api.oanor.com/emailparse-api
Temp Mail API
Disposable / temporary email as an API — no key, no signup. Spin up a throwaway mailbox in one call (you get back the address plus a token), then receive real inbound email and read it: list the inbox, open any message with its full HTML and plain-text body and attachments, mark messages seen, delete a single message, or delete the whole mailbox when done. List the available mailbox domains and look up account details (quota, usage). Perfect for sign-up flows, OTP / verification-code capture, QA and end-to-end test automation, and throwaway registrations. Inbox endpoints use a per-mailbox token returned by /v1/account/new (pass it as ?token= or an Authorization: Bearer header). Every call is live (no cache). 9 endpoints, backed by the public mail.tm service. Mailboxes are ephemeral. No upstream key, no cache.
api.oanor.com/tempmail-api
Frequently asked questions
Quick answers about pricing, quotas, and integration.
How do I get an API key for Email Normalize API?
Sign up for free at oanor.com, generate an API key from the developer dashboard, and call Email Normalize API with the x-oanor-key header. No credit card needed for the free tier.
What's the rate limit for Email Normalize API?
Free tier allows 1 request per second. Paid plans scale up to 50 requests per second on the Mega tier. Hard limits return HTTP 429 above the quota — no surprise overage charges.
How much does Email Normalize API cost?
Email Normalize API has a free tier with 100 calls / month. Paid plans start at €5.45 / month with higher quotas and faster rate limits.
Can I cancel my subscription anytime?
Yes. Plans are billed monthly and you can cancel anytime from your billing dashboard. No long-term contracts and no cancellation fee.
Is Email Normalize API GDPR-compliant?
All requests to Email Normalize API go through our EU-based gateway. Your upstream API key never leaves our server and no personal data is shared with the upstream provider beyond the request you send.
Pick an endpoint from the list on the left to see its details and try it.
Code snippets
Sign up to get an API key, then call any path under your slug.
curl https://api.oanor.com/emailnormalize-api/SOME_PATH \
-H "x-oanor-key: oanor_test_..."const res = await fetch("https://api.oanor.com/emailnormalize-api/SOME_PATH", {
headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();$ch = curl_init("https://api.oanor.com/emailnormalize-api/SOME_PATH");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-oanor-key: oanor_test_..."]);
$response = curl_exec($ch);import requests
r = requests.get(
"https://api.oanor.com/emailnormalize-api/SOME_PATH",
headers={"x-oanor-key": "oanor_test_..."},
)
print(r.json())Ratings
Sign in to rate.
No reviews yet.
Discussion
Ask questions, share usage tips, get answers from the provider and other developers. Public — anyone can read.
Sign in to start a thread or reply.
Sign inNew thread
📌 Pinned
🔒 Locked
·
·
·
-
Provider answer
🔒 This thread is locked — no new replies.
-
·
- No threads yet — start the discussion.
Support
Private 1:1 support with the provider — billing questions, integration issues, account problems. Only you and the provider team can see these threads.
Sign in to open a support ticket.
Sign inOpen new ticket
Describe what you need help with. The provider team gets an email and replies on the ticket page.
-
·
Urgent - No tickets yet for this API.