How to find someone's work email
To find someone's work email, start from their name and company domain: guess the company's address pattern and verify it, read the address off a public profile or signature, or send the name and domain to a lookup API that returns an address only when it finds one.
Start with two facts: the name and the company domain
Every route to a work email starts from the same two facts: the person's name as they use it at work, and the domain their company sends mail from. The domain matters more than the company name. "Example Corp" could be example.com, examplecorp.com or example.io; the address pattern lives on exactly one of them.
Get the domain from the company website, the company's profile page or a colleague's address you already hold. Strip "www." and lowercase it. If the company recently rebranded, check which domain still receives mail, because the old one often forwards for a while and then stops.
The Forager work email lookup takes these same two facts, a first name, a last name and a domain, or a LinkedIn public identifier on its own. Never both in one request; the API refuses a domain and an identifier together.
Route 1: guess the pattern, then verify
Most companies use one address pattern for everyone: first.last@, first@, flast@ or first_last@. If you know one colleague's address, you know the pattern. If you know none, generate the common patterns for the name and domain and test them.
A guess is worth nothing until a verifier accepts it. Mail servers that accept every address (catch-all domains) will accept your wrong guess too, so a "deliverable" result on a catch-all domain is not a yes. This is the step the page-1 guides tend to skip: expandi.io's guide (Aug 5, 2026) lists the patterns and the permutator tools but treats the guess as the answer.
- Good for: one person, a company whose pattern you already know, a quick sanity check.
- Not good for: a list, catch-all domains, people with common names at large companies (two Jane Does, one pattern).
Route 2: read it where it is published
Some people publish their work address. Look at the contact section of their professional profile, an email signature in a thread you were copied on, a byline on a company blog, a speaker page or a press release. Company "team" pages and GitHub commit histories sometimes carry addresses too.
This route is honest and free, and it takes minutes per person. It does not scale to a list, and a published address can be years old. Treat anything you find as a candidate to verify, not a fact.
Route 3: look it up by name and domain, or by a profile handle
A work email lookup does the pattern work for you and returns an address only when it finds one for that person at that domain. The Forager v2 lookup is asynchronous: the request returns a job id at once, and you poll the job until it completes. Polling is free.
Submit a lookup
curl -X POST https://api-v2.forager.ai/api/v2/{account_id}/datastorage/person_contacts_lookup/work_emails/ \ -H "X-API-KEY: $FORAGER_API_KEY" \ -H "Content-Type: application/json" \ -d '{"first_name":"Jane","last_name":"Doe","domain":"example.com"}'
import os, requests r = requests.post( f"https://api-v2.forager.ai/api/v2/{os.environ['FORAGER_ACCOUNT_ID']}/datastorage/person_contacts_lookup/work_emails/", headers={"X-API-KEY": os.environ["FORAGER_API_KEY"]}, json={"first_name": "Jane", "last_name": "Doe", "domain": "example.com"}, timeout=30, ) r.raise_for_status() data = r.json() if r.content else [] # an empty body means nothing was found
// illustrative values, not a record
{ "job_id": "7f3c…", "status": "queued" } Poll the job (GET …/work_emails/{job_id}/). The status moves through queued, running and awaiting_provider to completed or failed. A completed job carries a result of found or not_found; found jobs list the emails, each with its own validation status. While the job runs, a Retry-After header says when to poll again.
What it costs: 5 credits per lookup that finds an address, however many addresses it returns. A lookup that finds nothing costs 0 credits.
What a "not found" means
A miss is an answer. It means the lookup could not place that person at that domain with an address it would stand behind. Do not retry a clean not_found with the same input; the result will not change by asking again.
- result not_found, or a failed job with person_not_found, no_current_employer or input_unresolved: record the miss and move on. If you sent only a LinkedIn handle, one retry with the name and domain is reasonable.
- A failed job with provider_error, expired or internal_error: a retryable error, not a miss. Retry later, then pass the record on.
- A 429: you are polling too fast. Wait for the Retry-After value.
If Forager is one step in a waterfall, map found to "stop", not_found to "next step" and the error codes to "retry later". The waterfall step recipe in the docs shows the mapping as a table.
Work email or personal email?
A work address belongs to the employer. It stops working the day the person leaves, and it reaches them only while they read that inbox. For business outreach to someone at their current company, that is exactly what you want.
A personal email is the person's own webmail address and follows them between jobs. Recruiters, executive search and ad matching usually want that one instead. It is a separate lookup with its own rules; see the personal email guide below.
Doing it for a list or inside a product
For an enrichment run, use the bulk endpoint instead of one lookup per row. Submit a batch of items (each a name and domain, or a LinkedIn identifier), get a batch id back, and poll once for the whole batch or pass a webhook URL and let Forager call you.
Submit a batch
curl -X POST https://api-v2.forager.ai/api/v2/{account_id}/datastorage/person_contacts_lookup/work_emails/bulk/ \ -H "X-API-KEY: $FORAGER_API_KEY" \ -H "Content-Type: application/json" \ -d '{"email_lookups":[{"first_name":"Jane","last_name":"Doe","domain":"example.com"},{"linkedin_public_identifier":"jane-doe-example"}]}'
import os, requests r = requests.post( f"https://api-v2.forager.ai/api/v2/{os.environ['FORAGER_ACCOUNT_ID']}/datastorage/person_contacts_lookup/work_emails/bulk/", headers={"X-API-KEY": os.environ["FORAGER_API_KEY"]}, json={"email_lookups": [[object Object], [object Object]]}, timeout=30, ) r.raise_for_status() data = r.json() if r.content else [] # an empty body means nothing was found
// illustrative values, not a record
{ "batch_id": "b_91a…", "status_check_url": "…/bulk/b_91a…/" } - Duplicates in a batch collapse into one lookup, and items already answered by Forager's cache resolve at once.
- Your credit balance must cover the whole batch, or the batch is rejected and nothing is charged.
- The single lookup is rate limited for interactive use; batches are for runs.
Inside a product, keep the API key on your server, cache the result per person, and make the button idempotent so a user who clicks twice does not spend twice.
Before you send
Each returned address carries a validation status. Send to valid addresses. Hold risky ones until you have a second signal. Drop invalid ones. An address you guessed and never verified does not belong in a sequence at all.
The pieces this guide uses
Products
Recipes
- $5 free credits
- No credit card
- Run your sample
Questions about this guide
Can I find someone's work email for free?
Yes, for one person. Guess the company pattern and verify it, or read the address off a public profile, signature or byline. Both are free and take minutes per person. The cost is your time, and it does not scale to a list. For a list, a lookup API charges per address it finds.
How accurate is a guessed email address?
A guess is a hypothesis. It becomes an address only when a verifier accepts it, and on a catch-all domain even an accepted guess may be wrong. A lookup that returns an address with a validation status tells you what to do with it: send, hold or drop.
What if the person changed jobs?
The old work address stops working when they leave. Run the lookup again with the new company domain, or switch to a personal email, which follows the person. If you hold a list, re-check the current employer before you send.
Is it legal to look up a work email?
Business contact data is widely used for business-to-business outreach, and the rules differ by country. Record your lawful basis, keep an opt-out in every message and honor it. Bring your legal questions to a call and we take you through how Forager data is sourced.
Does a failed work email lookup cost anything?
No. A work email lookup is charged 5 credits only when it finds an address. A lookup that finds nothing costs 0 credits, and polling the job is free.
What is the difference between a work email finder and an email verifier?
A finder starts from a name and company and returns an address. A verifier starts from an address you already have and says whether a mailbox accepts it. Forager's work email lookup returns each address with its validation status, so the two steps come back together.
What do work emails cost for teams following this guide?
Work emails: 5 credits per work email found, and a work email lookup that finds nothing costs 0 credits. That is $0.07 per work email on Starter month to month and $0.05 on Pro with yearly billing. Self-serve plans are Starter, Growth, Pro and Scale. See plans and prices
Am I charged when no work email is found?
No. A work email lookup that finds nothing costs 0 credits, so you pay for work emails we find. Search, enrichment and reverse lookups are the exception: they are charged per request.
Is there a free way to try Forager?
Yes. Create a free account at app.forager.ai: it comes with $5 in free credits and an API key, and there is no credit card to sign up. Run it on records you already know, or book a demo and send us a list: we run it and show you what we find.
How do I know the data is right?
The test that counts is your own: send a list of profiles you care about. We run it and show you what we find, number by number, so you can measure hit rate and connect rate yourself.
Where does Forager data come from, and is it compliant?
Bring your legal and security questions to a call with our team, and we take you through how Forager data is sourced and the terms that cover work emails for teams following this guide. Forager's privacy policy is public, and anyone can send a request about their own personal data through the consumer rights form on forager.ai.
Is there a contract or minimum commitment?
No contract to start: a free account comes with $5 in credits. To keep using work emails, choose a monthly or yearly plan. Monthly plans cancel anytime and unused credits roll over; yearly plans grant all credits upfront and cost 10% less. Larger volumes are agreed with our team.
Written answers are not available right now. The matching pages above still help, or book a demo and ask the team.
- $5 free credits
- No credit card
- Run your sample
Related guides
Sources
- Forager docs: API credits and pricing (read Nov 1, 2026)
- Forager docs: Bulk work email lookup (read Nov 1, 2026)
- Forager docs: Waterfall enrichment with Forager (read Nov 1, 2026)
- Forager docs: Contact enrichment with the API (read Nov 1, 2026)
- expandi.io: How to Find Someone's Email for LinkedIn Outreach (Aug 5, 2026) (read Nov 1, 2026)
- inc.com: 10 Ways to Find Someone's Email Address for Free (Feb 13, 2018) (read Nov 1, 2026)