Email verification API

Check an email address before you send to it.

Send one address and get back what its mail server says: valid, invalid, catch-all, risky or unknown. No email is sent. It's the same check MagpieCRM runs before it saves a contact.

Join early access or see the planned prices

Status: Early access
You send: One email address
You get: valid, invalid, catch-all, risky or unknown
Also flags: Disposable, role and free-provider addresses
Planned price: 1 credit (£0.004$0.006) per address checked

Try it live

Check an address now.

This is our free email verifier, on the same verification servers the API will use. It checks 10 addresses a day, one at a time, and sends no email.

Recorded example: a real result from our free checker on 1 November 2026

Validpele@magpiecrm.com

The mail server says this mailbox exists. Safe to send.

Format: Valid
Domain takes email: Yes
Mailbox: Exists
Disposable address: No
Role address (info@, sales@): No
Free mailbox provider: No, a company domain

What the checker returned

{
  "email": "pele@magpiecrm.com",
  "verdict": "valid",
  "summary": "The mail server says this mailbox exists.",
  "checks": {
    "syntax": true,
    "domain": true,
    "provider": null,
    "mailbox": "exists",
    "disposable": false,
    "role": false,
    "free": false
  }
}

This uses the free checker, which runs on the same verification servers. The API's field names are planned and may change.

How it works

Asked of the mail server, not guessed.

Checks run from our own verification servers, so your domain and IP addresses are never used. A domain that accepts every address comes back as catch-all, not as valid.

How an address is checkedOur verification server asks the company's mail server whether jane.smith@northwind.example has a mailbox, the way a sending server would, and hangs up before sending anything.

Find the mail serverOur verification server to DNS
AsksMX northwind.example
Answermx.northwind.example
ConnectOur verification server to Company mail server
SendsOpens a connection
Reply220ready
Say helloOur verification server to Company mail server
SendsEHLO
Reply250hello
Name a senderOur verification server to Company mail server
SendsMAIL FROM
Reply250OK
Ask about the mailboxOur verification server to Company mail server
SendsRCPT TO:<jane.smith@northwind.example>
Reply250mailbox existsor550no such mailbox
Hang upOur verification server to Company mail server
SendsQUIT
Reply221bye
No email is sent. The check stops before DATA, the command that would carry a message.

Read the code:emailFinder.ts

Preview

What a call to the email verification API looks like.

This is how the API is planned to work. Names and fields may change before launch.

Request · POST /verify

curl https://api.magpie-cloud.com/v1/verify \
  -H "Authorization: Bearer $MAGPIE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "email": "alex.sample@examplefreight.example" }'

const res = await fetch("https://api.magpie-cloud.com/v1/verify", {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.MAGPIE_API_KEY}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({ email: "alex.sample@examplefreight.example" }),
});
const data = await res.json();

import os
import requests

res = requests.post(
    "https://api.magpie-cloud.com/v1/verify",
    json={"email": "alex.sample@examplefreight.example"},
    headers={"Authorization": f"Bearer {os.environ['MAGPIE_API_KEY']}"},
    timeout=90,
)
data = res.json()

Response

{
  "email": "alex.sample@examplefreight.example",
  "verdict": "valid",
  "summary": "The mail server says this mailbox exists.",
  "checks": {
    "syntax": true,
    "domain": true,
    "mailbox": "exists",
    "disposable": false,
    "role": false,
    "free": false,
    "provider": null
  }
}

Full reference: POST /verify

In MagpieCRM today

Every found email is checked before it's saved.

MagpieCRM on Magpie Cloud runs this check on every work email it finds. Save people from prospect search, and an address is saved as verified only when the company's mail server confirms it.

Catch-all and not-found results are flagged, not saved
No email is sent to check an address

Verified emails in MagpieCRM

MagpieCRM's Finding emails dialog: four people saved, each with a work email marked Verified

Early access

Get a key when it's ready.

The APIs aren't live yet. Tell us what you need, and we'll write when keys are ready.

Not yet

What it doesn't do yet.

The APIs are in early access. So you know before you sign up:

It isn't live yet: early-access members get keys first.
Verifying a whole list in one call is planned but not built.
The planned price may change before launch.

FAQ

Questions, answered.

Is the email verification API available now?

Not yet. It's in early access. Until then, the free email verifier checks 10 addresses a day, one at a time: try it on this page.

Does checking an address send an email?

No. The check stops before any message is sent, so the person never receives anything.

What does catch-all mean?

A catch-all domain accepts mail for every address, whether or not the mailbox exists, so its mail server never says no. The API can't tell whether a mailbox exists there, and says catch-all rather than guessing.

What will it cost?

The planned price is 1 credit (£0.004) for each address checked, the same as a verified email in MagpieCRM. It may change before launch.The planned price is 1 credit ($0.006) for each address checked, the same as a verified email in MagpieCRM. It may change before launch.

Keep exploring

Build on the engine behind MagpieCRM.

The APIs are in early access. Tell us what you'd use them for, and we'll write when your key is ready.

Join early access or read the API preview