Work Email Finder — Person & Company
Pricing
from $20.00 / 1,000 company contact emails
Find a verified work email from a name plus company domain, or a public LinkedIn handle — or discover the contacts at a whole company by domain or company name. Filter by department, seniority and decision-maker status. Bulk and CSV ready. No LinkedIn login, API key or proxy setup.
One person per line, in either form:
• Name, company — Jane Example, example.com or John Doe, Example Corporation. A domain is the most reliable identifier; a company name works too.
• LinkedIn profile URL — https://www.linkedin.com/in/example-person. On its own, with no name needed.
Every person you enter gets exactly one row back, including the ones that could not be found — so you always know which entries failed.
The LinkedIn URL is used only as an identifier. This Actor never opens the profile page and never needs a LinkedIn login, cookie or session.
[]Use this instead of the list above when you need your own CRM or spreadsheet key carried through to the output.
One object per person, with any of: fullName, firstName, lastName, domain, company, linkedinUrl, externalId.
If you supply both a domain and a company name, the domain is used.
[]Paste a CSV with a header row to look up many people at once. Every row here is treated as a person.
Recognised columns: full_name, first_name, last_name, company, domain, linkedin_url, external_id.
Each row needs either a name plus a company or domain, or a LinkedIn URL on its own. A row with neither comes back as a row explaining why, rather than being silently dropped. Unrecognised columns are ignored rather than guessed at.
One company per line. Domains, websites and company names all work: stripe.com, www.stripe.com, https://stripe.com/jobs, Stripe.
A company name is resolved to its domain first, and is only searched when the match is confident — a weak match is reported rather than guessed at, because searching the wrong company costs you money and returns the wrong people.
Consumer mail domains such as gmail.com are rejected; they are not companies.
This returns the contacts Hunter has indexed for the domain. It is not a guaranteed list of every employee.
[]Use this instead of the list above when you need your own account key carried through to the output.
[]Paste a CSV with a header row to search many companies at once. Every row here is treated as a company.
Recognised columns: company, domain, external_id.
Each row needs a domain or a company name. A row with neither comes back as a row explaining why, rather than being silently dropped. Unrecognised columns are ignored rather than guessed at.
The most contacts to return for any one company. Lowering this genuinely costs less: the provider is asked for exactly this many, rather than a full page that then gets trimmed.
Keep only contacts in these departments. Applied by the provider before results are returned, so narrowing here reduces what you are charged rather than filtering after the fact.
[]Keep only the contacts the provider flags as decision makers for their department.
"Personal" means an individual's work address (jane@company.com). "Generic" means a shared company inbox (info@, sales@, support@).
Personal only by default. Adding generic inboxes returns more rows — and more rows are charged — so turn it on when a shared inbox is genuinely useful to you.
[ "personal"]A hard ceiling on the number of rows containing an email address, across both person and company results. This is the one setting that bounds what a run can cost you.
It is enforced before the provider is called, so inputs beyond the ceiling are never paid for. Rows explaining a miss, an error or an empty company are always returned and never count towards it.
Off by default. Every address already arrives with the verification status the provider recorded when it indexed the address — valid, accept_all, webmail or unknown — and that costs you nothing extra.
Turn this on to re-check each address live instead, which adds SMTP-level detail (MX records, SMTP check, catch-all, disposable, gibberish) and a fresh per-address score. It is charged as its own event, once per address checked. Worth it before sending to a list that has been sitting for a while.
On an accept-all domain it cannot change the verdict. Those mail servers accept every address, so no live check can confirm one mailbox — the status stays accept_all and isVerified stays false, however high the score. You still get the SMTP detail and a per-address score that varies where the indexed confidence score does not, which is the only signal available for ranking contacts at such a domain. Decide with that in mind, because you are charged per address either way.