Email Finder API: find work emails by name and company domain
Find a person's work email from their name and company. Use it to enrich your CRM, route inbound leads or build outbound lists.
https://api.envoapi.com/v1/emails/find- 100 free credits
- No credit card
- REST + JSON
findEmailillustration- InputJane Doe @ example.com
- Formatsjane, jane.doe, jdoe, j.doe +26 built
- MXmx.example.comfound
- Check 1jane@example.comrejected
- Check 2jane.doe@example.comaccepted
- jane.doe@example.com
- found
- candidatesChecked
- 2
- creditCost
- 10
- emails sent
- 0
- cached
- never
Overview
How the Email Finder API works
- 10credits per completed search, on every plan
- ≤16formats checked per search, in a fixed order
- 0emails sent to the person you look up
- Liveevery call is a fresh check, never a cached result
Send a name and company domain
Send the person's name and their company's domain, such as Jane Doe and example.com.
Find the email
We try the email formats companies use most and check each one with the company's mail server. No email is sent.
Return the found email
We return the confirmed work email with its verification details, ready to use.
Results
What the API returns
| status | What it means | What to do | |
|---|---|---|---|
| found | jane.doe@example.com | The mail server accepted one of the formats. You get the address and the server's verdict. | Save it and send to it. |
| catch_all | null | The server accepts every address, so no single email can be confirmed. isCatchAll is true. | Use another channel or a lower-priority sequence. |
| not_found | null | Every format was rejected, or the domain is a disposable email service (isDisposable true). | Drop disposable domains. Retrying gives the same answer. |
| no_mx | null | The domain has no MX record, so there is no mail server to check. | Check the domain for a typo. |
Request
Make your first request
| Parameter | Description |
|---|---|
firstName required1 to 64 characters, at least one letter | The person's first name. Accents and capitals are fine. |
lastName optional1 to 64 characters, at least one letter | The person's last name. Leave it out and only first-name formats are tried, so send it when you have it. |
domain required3 to 253 characters, like example.com | The company's email domain. Send the bare domain, not a URL or an address. |
Authorization headerBearer token | Bearer followed by your API key. Keep the key on your server. |
curl -G "https://api.envoapi.com/v1/emails/find" \ -H "Authorization: Bearer $ENVO_API_KEY" \ --data-urlencode "firstName=Jane" \ --data-urlencode "lastName=Doe" \ --data-urlencode "domain=example.com"import osimport requestsresponse = requests.get( "https://api.envoapi.com/v1/emails/find", headers={"Authorization": f"Bearer {os.environ['ENVO_API_KEY']}"}, params={"firstName": "Jane", "lastName": "Doe", "domain": "example.com"},)result = response.json()["data"]const url = new URL("https://api.envoapi.com/v1/emails/find");url.searchParams.set("firstName", "Jane");url.searchParams.set("lastName", "Doe");url.searchParams.set("domain", "example.com");const response = await fetch(url, { headers: { Authorization: `Bearer ${process.env.ENVO_API_KEY}` },});const { data } = await response.json();req, _ := http.NewRequest(http.MethodGet, "https://api.envoapi.com/v1/emails/find", nil)req.Header.Set("Authorization", "Bearer "+os.Getenv("ENVO_API_KEY"))query := req.URL.Query()query.Set("firstName", "Jane")query.Set("lastName", "Doe")query.Set("domain", "example.com")req.URL.RawQuery = query.Encode()res, err := http.DefaultClient.Do(req)Response fields
| Field | Type | Description |
|---|---|---|
data.email | string | null | The accepted address. Present only when status is found. |
data.status | enum | found, catch_all, not_found or no_mx. |
data.candidatesChecked | integer | How many addresses were checked, from 0 to 16. |
data.isCatchAll | boolean | True when the domain accepts every address. |
data.isDisposable | boolean | True when the domain is a known throwaway email provider. |
data.verification | object | null | The mail server we asked (mx), its verdict (status) and a stable reason code. |
meta.creditCost | integer | Credits charged for this search: 10. |
Errors
What each error means and what to do
| HTTP | code | Credits | Retry | Why |
|---|---|---|---|---|
422 | email_unverifiable | refunded | Do not retry | Emails on this domain can't be verified. Credits are refunded. |
503 | capacity_exceeded | refunded | Retry after the Retry-After delay | The verification provider is full right now. Credits are refunded. Wait for the number of seconds in the Retry-After header, then send the same request again. |
429 | rate_limit_exceeded | not charged | Wait, then retry | Your API key sent more requests per minute than your plan allows. Nothing is charged. Slow down and retry after the Retry-After delay. |
402 | insufficient_credits | not charged | Top up, then retry | Your account has fewer than 10 credits left. Nothing is charged. Watch the X-Credits-Remaining header on every response to see it coming. |
400 | invalid_request | not charged | Fix the request | A parameter is missing or breaks a rule above. Nothing is charged. The error details name the field. |
Pricing
Email Finder API pricing
| Plan | Price | Searches | Per search | Rate limit |
|---|---|---|---|---|
| Free | $0 | 10, one time | — | 10 RPM |
| Launch | $49/mo | 1,000 | $0.049 | 60 RPM |
| GrowthFits | $149/mo | 5,000 | $0.03 | 120 RPM |
| Scale | $499/mo | 25,000 | $0.02 | 300 RPM |
| Volume | $1,799/mo | 100,000 | $0.018 | 600 RPM |
| Enterprise | Custom | 200,000+ | Custom | Custom |
Use cases & tips
Use cases and tips
CRM
Fill missing emails in your CRM
Most CRMs have contacts with a name and a company but no email. Run them through the finder and write back only confirmed addresses.
- CRM contact
- Find Email
- email field
Inbound
Reach inbound leads faster
When a form gives you a name and company, find the work email before the lead reaches sales. No domain? Get it from the LinkedIn Company API first.
- Company API
- Find Email
- lead owner
Outbound
Build outbound lists
Find people at your target companies with the LinkedIn Search API, then run each one through the Email Finder to get an address you can send to.
- People search
- Find Email
- Verify Email
Tip 01
Send the full name
Without a last name only first-name formats are tried, which rarely match at larger companies.
Tip 02
Store the result on your side
Results are never cached by EnvoAPI. If you search the same person twice, you pay twice, so save what you get.
Tip 03
Treat catch_all as unconfirmed
A catch-all server accepts anything, so the address could still bounce. Route these contacts to another channel.
Pick the right email endpoint
| Endpoint | Send | Get back | Credits | Use it when |
|---|---|---|---|---|
| Email Finder this page | Name + company domain | A confirmed work email, or the reason there is none | 10 | You know who you want to reach but not their address. |
| Email Verification | One email address | valid, invalid or unverifiable, with catch-all and disposable flags | 2 | You already have an address and want to know if it is safe to send to. |
| Disposable Email Check | One email address | Whether the domain is a throwaway inbox | 0 | You want to block temporary inboxes at signup without spending credits. |
FAQ
Email Finder API FAQ
Still unsure? The API reference has the full schema and every error.
What does an email finder API do?
It turns a person's name and their company's domain into a work email address. EnvoAPI builds the email formats companies use most, checks them with the company's mail server in order, and returns the first one the server accepts.
How accurate is the Email Finder API?
We only return an address the company's mail server has accepted. If the server accepts everything (a catch-all), rejects every format, or the domain is a disposable email service, the status tells you so. You never get an address that was not confirmed.
Do you send an email to check the address?
No. Each address is checked with the company's mail server directly. The person never receives a message.
Which email formats are tried?
Common work-email formats built from the first and last name, such as jane, jane.doe and jdoe, in a fixed order, up to 16 per search. The search stops at the first address the server accepts, and candidatesChecked tells you how many were tried. If the server reports a format as disposable, the search stops there with no address.
Is the last name required?
No. firstName and domain are required and lastName is optional. Without a last name only first-name formats are tried, so send the full name when you have it.
Is the Email Finder API free?
You get 100 free credits, enough for 10 searches, with no credit card. After that, every completed search costs 10 credits, whether the result is found, catch_all, not_found or no_mx. Paid plans start at 10,000 credits a month, which is 1,000 searches.
Why is a search charged when no address is found?
Because the check still ran: we found the mail server and tested each format. not_found and catch_all are real answers, and they tell you not to spend more time on that address. Errors are never charged.
What should I do with a catch-all domain?
Treat it as unconfirmed. The domain accepts every address, so no single one can be confirmed and EnvoAPI returns no email. If you need to contact the person anyway, use a different channel or expect a possible bounce.
Does it work for Gmail or other personal addresses?
Not really. It is built for company domains. A gmail.com address the server accepts may belong to someone else with the same name. Yahoo, ymail.com and rocketmail.com can't be checked at all: those searches return 422 email_unverifiable and the credits are refunded.
Are results cached?
No. Every call is a fresh check with the mail server, so the response has no cache status. Save results on your side if you may need them again.
Can I find emails in bulk?
There is no bulk endpoint. Send one request per person and run them in parallel, up to your plan's rate limit.
Find your first work email
100 free credits is 10 searches. No credit card required.