Find a Person's Work Email From a LinkedIn URL or Their Name and Domain

The email finder finds a person’s deliverable work email. Send either:

a LinkedIn profile URL: we find the person’s work email at their current employer, or
a first name, last name, and company domain.

Either way, you get a verified email back. This guide uses the credit-metered endpoint. On an unlimited plan, the same workflow applies at POST /v1/unlimited/email-lookup with an Unlimited key; searches draw on your monthly cap instead of credits.

When to use the email finder

LinkedIn prospecting: you have a list of LinkedIn profile URLs and need a work email for each person.
Contact enrichment: you’ve collected a name and company from a form or a CSV and need a reachable email to act on it.
Lead research: you know who you want to contact and where they work, but not the exact address.
Reconnecting with known contacts: find a contact’s new work email after their company moves from a free email provider to its own domain.

For verifying an address you already have, use single verification. For verifying a list of known addresses, use bulk verification.

Finding emails for more than one person? Use the bulk email finder. For best results, use it where possible, as it allows more time per entry. Use the single email finder only for one-off searches, or when your tool (such as Clay) doesn’t support bulk.

Making a request

This section uses a name and domain. To start from a LinkedIn profile instead, see Search by LinkedIn profile URL. To find an email, send a POST request to /v1/email-lookup with the person’s company domain and at least one of their first and last name in the JSON body. Include your API key in the X-API-Key header.

Get your API key

Send the request

Call POST /v1/email-lookup with your key in the request header.

curl --request POST \
  --url "https://api.orbisearch.com/v1/email-lookup" \
  --header "X-API-Key: YOUR_API_KEY" \
  --header "Content-Type: application/json" \
  --data '{
    "first_name": "Jane",
    "last_name": "Doe",
    "domain": "acme.com"
  }'

import requests

response = requests.post(
    "https://api.orbisearch.com/v1/email-lookup",
    json={
        "first_name": "Jane",
        "last_name": "Doe",
        "domain": "acme.com",
    },
    headers={"X-API-Key": "YOUR_API_KEY"},
)

result = response.json()
print(result["email"], result["status"])

const response = await fetch(
  "https://api.orbisearch.com/v1/email-lookup",
  {
    method: "POST",
    headers: {
      "X-API-Key": "YOUR_API_KEY",
      "Content-Type": "application/json",
    },
    body: JSON.stringify({
      first_name: "Jane",
      last_name: "Doe",
      domain: "acme.com",
    }),
  }
);

const result = await response.json();
console.log(result.email, result.status);

Read the response

When a deliverable address is found, the response includes the discovered email and the same enrichment fields as single verification.

{
  "first_name": "Jane",
  "last_name": "Doe",
  "domain": "acme.com",
  "email_domain": "acme.com",
  "linkedin_url": null,
  "email": "jane.doe@acme.com",
  "status": "safe",
  "substatus": "deliverable",
  "explanation": "Safe to email. The mailbox exists and is deliverable.",
  "confidence": 98,
  "full_name": null,
  "employer_name": null,
  "employer_linkedin_url": null,
  "all_emails": null,
  "email_provider": "Google Workspace",
  "mx_record": "aspmx.l.google.com",
  "is_domain_catch_all": false,
  "is_secure_email_gateway": false,
  "is_disposable": false,
  "is_role_account": false,
  "is_free": false,
  "credits_consumed": 1
}

Search by LinkedIn profile URL

Send linkedin_url on its own, without first_name, last_name, or domain. Use the profile URL in its usual form, such as https://www.linkedin.com/in/jane-doe.

curl --request POST \
  --url "https://api.orbisearch.com/v1/email-lookup" \
  --header "X-API-Key: YOUR_API_KEY" \
  --header "Content-Type: application/json" \
  --data '{
    "linkedin_url": "https://www.linkedin.com/in/jane-doe"
  }'

import requests

response = requests.post(
    "https://api.orbisearch.com/v1/email-lookup",
    json={"linkedin_url": "https://www.linkedin.com/in/jane-doe"},
    headers={"X-API-Key": "YOUR_API_KEY"},
)

result = response.json()
print(result["email"], result["employer_name"], result["status"])

const response = await fetch(
  "https://api.orbisearch.com/v1/email-lookup",
  {
    method: "POST",
    headers: {
      "X-API-Key": "YOUR_API_KEY",
      "Content-Type": "application/json",
    },
    body: JSON.stringify({
      linkedin_url: "https://www.linkedin.com/in/jane-doe",
    }),
  }
);

const result = await response.json();
console.log(result.email, result.employer_name, result.status);

The response has the same fields as a search by name and domain. The person and employer fields, which are null in a search by name and domain, are filled in:

{
  "first_name": "Jane",
  "last_name": "Doe",
  "domain": "acme.com",
  "email_domain": "acme.com",
  "linkedin_url": "https://www.linkedin.com/in/jane-doe",
  "email": "jane.doe@acme.com",
  "status": "safe",
  "substatus": "deliverable",
  "explanation": "Safe to email. The mailbox exists and is deliverable.",
  "confidence": 98,
  "full_name": "Jane Doe",
  "employer_name": "Acme",
  "employer_linkedin_url": "https://www.linkedin.com/company/acme",
  "all_emails": [
    {
      "email": "jane.doe@acme.com",
      "job_order": 1,
      "company_linkedin_url": "https://www.linkedin.com/company/acme",
      "email_domain": "acme.com"
    }
  ],
  "email_provider": "Google Workspace",
  "mx_record": "aspmx.l.google.com",
  "is_domain_catch_all": false,
  "is_secure_email_gateway": false,
  "is_disposable": false,
  "is_role_account": false,
  "is_free": false,
  "credits_consumed": 1
}

Field	What it contains
`linkedin_url`	The profile URL the result is for, in its standard form.
`full_name`	The person’s full name.
`first_name`, `last_name`	The person’s first and last name.
`domain`	The company’s website domain. `null` when we couldn’t determine one.
`email_domain`	The domain the company hosts its email on. `null` when there’s no domain.
`employer_name`	The person’s current employer.
`employer_linkedin_url`	The LinkedIn URL of the current employer.
`all_emails`	Every work email found for this person. Empty when none was found.

For a name and domain request, the LinkedIn fields are null. A search by LinkedIn URL can also return these substatuses, with status: unknown and email: null:

`substatus`	What it means
`profile_not_found`	The URL is a correctly formed LinkedIn profile URL, but not a valid profile, for example mistyped or no longer in use. Check that the URL is correct and current.
`no_current_employer`	We couldn’t identify a current employer for this person. `full_name` is still returned.
`no_company_website`	The person has a current employer, but we couldn’t identify a company website for it. `full_name` and `employer_name` are still returned. If you know the company’s website, search for the person by name and domain instead.

When no address is found, the substatus is no_address_found, with employer_name, employer_linkedin_url, domain, and email_domain filled in. A URL that isn’t a LinkedIn profile URL (for example a company page URL, or not a URL at all) is rejected with 422 and no credit is charged. So is a request that sends linkedin_url together with a name or domain.

Interpreting the response

The top-level status uses the same vocabulary as /v1/verify:

`status`	`substatus`	What it means
`safe`	`deliverable`	We found a deliverable address for this person. The `email` field contains it.
`unknown`	`no_address_found`	We couldn’t confirm a deliverable address for this person at this domain. The `email` field is `null`.
`unknown`	`profile_not_found`, `no_current_employer`, `no_company_website`	Searches by LinkedIn URL only. See Search by LinkedIn profile URL.
`unknown`	`timeout`	The search hit the per-request time budget before completing. For best results, use the bulk email finder where possible, as it allows more time per entry.

For a name and domain request, the response echoes the first_name, last_name, and domain you sent (with casing and whitespace cleaned up), and includes credits_consumed. When a deliverable address is found, the full set of verification fields (email_provider, mx_record, enrichment flags) is populated. See Single Verification: Response Fields for their meaning. When email is null, don’t send to that person at that domain. We couldn’t find a deliverable address for them.

Pricing

Each search costs 1 credit, whether you send a LinkedIn URL or a name and domain. Every returned response is charged, including profile_not_found, no_current_employer, no_company_website, substatus: timeout (the search ran but did not complete within your timeout value) and repeat searches for the same person. Refunds are issued only when OrbiSearch infrastructure cannot complete the request (502).

Rate limits

This endpoint shares the 20 requests per second per account limit with /v1/verify and /v1/bulk.

The `timeout` parameter

By default, OrbiSearch waits up to 97 seconds for the search to complete. You can override this with the timeout field in the request body (minimum 30, maximum 97, in seconds).

curl --request POST \
  --url "https://api.orbisearch.com/v1/email-lookup" \
  --header "X-API-Key: YOUR_API_KEY" \
  --header "Content-Type: application/json" \
  --data '{
    "first_name": "Jane",
    "last_name": "Doe",
    "domain": "acme.com",
    "timeout": 60
  }'

If the search hits the timeout, you receive a status: unknown / substatus: timeout response. The credit is charged like any other returned response. For best results, use the bulk email finder where possible, as it allows more time per entry.

Get Started

Core Concepts

Guides

Find a Person's Work Email From a LinkedIn URL or Their Name and Domain

When to use the email finder

Making a request

Search by LinkedIn profile URL

Interpreting the response

Pricing

Rate limits

The `timeout` parameter

​When to use the email finder

​Making a request

​Search by LinkedIn profile URL

​Interpreting the response

​Pricing

​Rate limits

​The timeout parameter

When to use the email finder

Making a request

Search by LinkedIn profile URL

Interpreting the response

Pricing

Rate limits

The `timeout` parameter