Company Email Pattern API: Find the Format a Company Uses

A company email pattern API returns the format a business uses for staff addresses, such as first.last@domain, along with mail-server facts like MX records and catch-all status. It does not return anyone’s actual address. Used carefully, it supports outreach research; used carelessly, it encourages guesswork that harms deliverability.

What the endpoint returns

The BusinessMCP Company Data API lists an email pattern endpoint at GET /api/hub/v1/companies/{domain}/email-pattern, priced at $0.01 per call. According to the page, it returns the address format a company uses, for example first.last, plus MX and catch-all status, and no personal addresses. Its comparison page adds that the service does not perform SMTP verification, which matters for how you use the result.

Reading the three outputs

Output	Meaning	Practical impact
Pattern (e.g. first.last)	The usual local-part format	Lets you form a candidate address from a known name
MX status	Domain is set up to receive mail	If absent, do not send
Catch-all	Server accepts any address	Bounces will not reveal bad guesses

Key takeaway: a pattern gives you a candidate address, not a verified one. Verification is a separate step, and the pattern endpoint is not it.

Appropriate uses

• Research and planning. Learn whether a target uses first.last or an initial-plus-surname format before building a sequence.
• Data quality. Check that known contacts’ addresses follow the company’s format; outliers are typos or aliases.
• Domain health. A domain without MX is a red flag for outreach.
• Validation design. Choose which verification checks to run based on catch-all status.

Risks of guessing addresses

Generating addresses from names and a pattern, then sending, causes bounces. High bounce rates damage sender reputation and can land you in spam filters. On catch-all domains the damage is hidden, since the server accepts everything and bounces arrive later or never. If you do build candidate addresses, verify them with a dedicated verification step. The comparison page mentions separate pricing for email verification at $0.002 and an email finder at $0.04 that requires a card, as stated for BusinessMCP; check the live pricing page before relying on that.

Privacy and compliance

Emailing individuals at work is regulated in many places, and rules vary on consent, legitimate interest and opt-out. Constructing an address for a named person is processing personal data. Take advice on your lawful basis and honour opt-outs. This article gives no legal advice, and rules change, so check current requirements for your markets.

A responsible workflow

1. Identify target accounts, for example through company search.
2. Confirm sites are live using website status.
3. Pull email pattern, MX and catch-all status.
4. Skip domains without MX.
5. For catch-all domains, be cautious: use alternative channels or verified contacts.
6. Verify any candidate address before sending.
7. Keep opt-out and suppression lists.

Pattern versus finder versus verifier

These three are often sold together and confused:

• Pattern: the format, company-level.
• Finder: tries to return a specific person’s address.
• Verifier: checks whether an address is likely deliverable.

The pattern endpoint is the first, and the lightest in terms of privacy exposure, since it carries no personal data according to the provider. If you need the others, treat them as separate products with separate legal and cost profiles. See our look at work email lookups for the opposite direction, from an email to a company.

Cost and volume

At $0.01 per call, checking patterns for 5,000 target domains costs about $50 at the stated price, subject to the provider’s found-based billing. Cache patterns for weeks; formats rarely change. For a general view of how these small prices add up, see company data API pricing.

Limits worth stating

Patterns can be inferred from limited samples, so a result may not describe every employee: executives, shared inboxes and legacy staff often differ. Treat the pattern as the most common format, not the only one. And remember that no pattern API can tell you whether a particular person works at the company today.

Worked example of reading a pattern result

Say a pattern lookup for a mid-sized firm returns first.last, MX present and catch-all false. That combination is the best case: the company uses a predictable format, can receive mail, and its server will reject unknown mailboxes, so a verification step can tell you something useful. Now imagine the same lookup returns first.last, MX present, catch-all true. The format is still useful for planning, but you cannot learn from bounces whether a given address exists, so you should rely on verified contacts or other channels. A third case, no MX, means the domain cannot receive email at all and should be removed from email outreach lists.

Common pattern formats

Format	Example for Jane Doe	Notes
first.last	jane.doe@	Very common in larger firms
first	jane@	Common in small teams; collisions are resolved by suffix
flast	jdoe@	Initial plus surname
firstl	janed@	First name plus initial
last.first	doe.jane@	Less common

Real companies mix formats over time, particularly after mergers, so a pattern describes the majority only.

Pairing with company data

An email pattern is most useful next to the firmographics that tell you whether the company is worth contacting at all. Use the BusinessMCP Company Data API lookup for size, industry and location, then the pattern endpoint only for accounts that pass your filter. That order saves money: at the listed prices, a lookup is $0.02 and a pattern check is $0.01, so skipping pattern calls for accounts you will not contact is a direct saving. For finding the accounts in the first place, see company search.

Operational tips

• Cache patterns for weeks; formats rarely change.
• Record the date and the source with each pattern.
• Keep a suppression list and check it before any send.
• Never use a pattern to build addresses for people who have opted out.
• Monitor bounce rate and complaint rate after each campaign; stop if they rise.

For the reverse direction, starting from an address and finding the company, read work email to company lookup, and for broader checks on a domain before outreach see domain to company API.