Role Account Detection API
Shared inboxes like info@ and sales@ are not people. Flag them at capture so you can gate signups, adjust lead scores, or suppress them from cold sends.
What Mailbeam checks
Every verification runs 7 checks in parallel and returns a structured result in under 100ms.
Curated role-prefix database
Matches against a maintained list of role prefixes — info, admin, support, sales, billing, noreply, and dozens more — normalized for sub-addressing (info+tag@).
Returns a boolean plus context
The response flags role: true and still runs every other check, so you keep the full deliverability verdict rather than a bare yes/no.
Sub-addressing aware
info+newsletter@ is correctly identified as the info@ role account, not treated as a unique personal mailbox.
Locale-aware prefixes
Recognizes common non-English role prefixes (kontakt@, ventas@, contato@) so international lists aren't under-flagged.
Tunable enforcement
Role accounts are flagged, not auto-rejected — you decide whether to block, route to sales, or simply down-score them.
Runs inline in one call
Role detection is part of the same /v1/verify response, adding no extra request or latency to your flow.
How it works
POST the address
Send the email to /v1/verify. Role detection runs alongside syntax, MX, SMTP, and disposable checks.
Local-part is normalized
The part before the @ is lowercased and stripped of +tag sub-addressing before matching.
Prefix match against the database
The normalized local-part is checked against the maintained role-prefix set, including localized variants.
Flag returned in the result
role: true|false comes back in the JSON alongside status and score, so you branch on it in code.
Integrate in minutes
const res = await fetch("https://api.mailbeam.dev/v1/verify", {
method: "POST",
headers: { Authorization: `Bearer ${process.env.MAILBEAM_KEY}` },
body: JSON.stringify({ email }),
});
const { role, status } = await res.json();
if (role) {
routeToSalesAssist(email); // shared inbox — don't self-serve
} else if (status === "deliverable") {
allowSelfServeSignup(email);
}When to use it
B2B signup gating
Route info@ and admin@ signups to a sales-assist flow instead of self-serve, where a shared inbox rarely converts.
Cold outreach suppression
Suppress role accounts before a cold send — they generate complaints and rarely belong to a single decision-maker.
Lead scoring
Down-weight role accounts in your scoring model since they signal a shared inbox, not an individual buyer.
List segmentation
Separate personal from departmental addresses so you can message each appropriately.
Frequently asked questions
Ready to integrate?
Free tier includes 1,000 verifications/month. No credit card required.