How to find anyone's work email using the email Finder API

Finding a work email address is not always as simple as guessing first.last@company.com. Many organizations use multiple domains, identity providers, aliases, and catch-all configurations that make pattern-based email finding unreliable.

The Relentless Identity Finder API solves this differently. It starts with a real name and a public company domain, then performs domain discovery and identity verification to resolve the most likely work email identity.

If you are still deciding whether you need discovery or just mailbox validation, see Identity verification vs. email verification.

What the Finder expects

Start with the best person-level information you have and the domain your users already recognize.

{
  "full_name": "John Smith",
  "email_domain": "company.com"
}

You do not need to know the final mailbox domain. If the company's email domain differs from its public website domain — which is common in acquired companies, regional operations, or identity-provider-managed tenants — the Finder handles that discovery work.

What you get back

The Finder returns a compact response with the same top-level shape as Probe: state, outcome, and address.

• state is deliverable when the identity is verified.
• outcome describes the verification result.
• address contains the resolved email when Finder finds a match.

Additional context may include identity_providers and mx_hosts when those signals are available.

How the Finder differs from pattern-based email finders

Traditional email finders infer likely addresses from naming patterns. If a company uses first.last@company.com, the tool generates guesses for other employees and validates them with SMTP probing.

That approach works when the company has a consistent pattern and the target identity follows it. It breaks when:

• The company uses multiple email domains.
• The mailbox domain differs from the website domain.
• Aliases or forwarding rules obscure the primary address.
• Catch-all behavior makes SMTP probing ambiguous.
• Identity providers manage the mail routing.

The Relentless Identity Finder is built for these harder cases. Instead of guessing patterns, it performs identity-first discovery: it finds related email domains, verifies the person against live identity and mailbox signals, and resolves aliases when detected.

Use cases for the email Finder API

Sales and outreach

When a sales rep needs to reach a specific person at a target account, the Finder provides a verified work email without relying on guessed patterns. This reduces bounce rates and improves the quality of outreach sequences.

CRM enrichment

When your CRM contains a person's name and company but not their email, the Finder fills the gap with a verified identity. The result can be stored directly in the CRM because it carries a deliverable signal.

Recruiting

When a recruiter needs to contact a candidate at their current employer, the Finder resolves the work email from the candidate's name and company domain. This is especially useful when the candidate's email is not publicly listed.

Fraud and underwriting

When a risk team needs to verify that an applicant's work email belongs to a real person at the stated company, the Finder provides identity-level confidence rather than just deliverability.

Onboarding and account verification

When a SaaS platform needs to verify that a new user's work email corresponds to a real identity, the Finder can validate the address during signup or onboarding.

Pairing Finder with Probe

The Finder resolves the most likely work email identity. For more on the difference between mailbox checks and identity checks, see Identity verification vs. email verification. When you need additional verification on a specific address, pair it with Probe.

A common workflow:

1. Call Finder with a name and domain to resolve the likely email.
2. Store the resolved address.
3. Call Probe on the resolved address to confirm deliverability before sending.

This two-step pattern gives you both discovery and verification in a single workflow.

Getting started

For a look at why SMTP probing fails behind gateways, see Why email gateways return hard bounces for valid addresses. See the REST API reference for the full endpoint specification, or read the response semantics guide to understand how to interpret results in your application.

If you want to try the Finder flow before integrating, use the free email finder. If you are building agents, the MCP workflows post shows how Finder fits into the same system.