🔍

Role Account Detector

Detect whether an email address is a role/group account or personal mailbox

GET 1 credit /v1/email/role-check

curl "https://email.toolkitapi.io/v1/email/[email protected]" \
  -H "x-api-key: YOUR_API_KEY"

import httpx

resp = httpx.get(
    "https://email.toolkitapi.io/v1/email/[email protected]",
)
print(resp.json())

const resp = await fetch("https://email.toolkitapi.io/v1/email/[email protected]", {
});
const data = await resp.json();
console.log(data);

# See curl example

Response 200 OK

{
  "email": "[email protected]",
  "local_part": "admin",
  "domain": "company.com",
  "is_role": true,
  "role_type": "administrative"
}

Description

Detect whether an email address is a role/group account or personal mailbox

How to Use

1

1. Pass the email address as the `email` query parameter.

2

2. Check `is_role` — `true` means it's a role/group account.

3

3. Review `role_type` for the category of role account (administrative, support, sales, etc.).

4

4. Use this information to filter or score leads in your email marketing pipeline.

About This Tool

The Role Account Detector classifies an email address as either a role/group account or a personal mailbox. Role accounts like admin@, support@, info@, sales@, and noreply@ are shared mailboxes that typically don't represent individual people.

Knowing whether an address is a role account is important for email marketing compliance, lead scoring, and deliverability. Role accounts often have different engagement patterns and may be less valuable as marketing contacts.

The detector categorizes role accounts into types: administrative, support, general, sales, finance, security, automated, human_resources, technical, legal, marketing, group, and executive.

Why Use This Tool

Lead scoring — Deprioritize role accounts in favor of personal email addresses
Email marketing compliance — Identify and handle role accounts differently in campaigns
CRM data enrichment — Tag contacts as role vs. personal for segmentation
Sign-up quality filtering — Flag role account sign-ups for review

Frequently Asked Questions

What local parts are considered role accounts?

Common role prefixes include: admin, support, info, sales, billing, hr, noreply, abuse, security, webmaster, postmaster, marketing, legal, dev, ops, and many more — over 60 patterns are recognized.

Is this just pattern matching on the local part?

Yes, role detection is based on the local part (before @) matching known role account patterns. It does not make network calls, making it extremely fast.

Can a personal email look like a role account?

Rarely, but it's possible. Someone named "Sal Sales" might use `sales@...` as a personal address. The detection is heuristic-based and optimized for the common case.

Start using Role Account Detector now

Get your free API key and make your first request in under a minute.

Get Free API Key View Docs