Find Work Emails in Bulk From LinkedIn URLs or Names and Domains

A bulk email finder job finds deliverable work emails for a list of people in a single asynchronous job. Submit a list of LinkedIn profile URLs, or a list of rows with a name and company domain; OrbiSearch processes them in the background and returns a verified result for each. This guide uses the credit-metered endpoints. On an unlimited plan, the same workflow applies at the /v1/unlimited/bulk-lookup paths with an Unlimited key; rows draw on your daily cap instead of credits.

When to use the bulk email finder

LinkedIn lists: turn a list of LinkedIn profile URLs into reachable work emails.
List enrichment: turn a CSV of names + companies into a list of reachable emails.
Lead research at scale: research a target list once, instead of one address at a time.
Keeping a list current: people change jobs, so search your LinkedIn profile URLs again every few months to find each person’s current work email.

To find one person’s email on demand, use the single email finder. For verifying a list of email addresses you already have, use bulk verification.

How the bulk email finder works

Submit a job

Send a POST request to /v1/bulk-lookup with an input array of rows. Every row is a linkedin_url, or every row is a (first_name, last_name, domain) object; one job uses one kind. OrbiSearch returns a job_id immediately and begins processing in the background. Credits are deducted upfront for the unique row count.

Poll for status

Use GET /v1/bulk-lookup/{job_id} to check the job’s progress. Poll every 10–30 seconds until status becomes completed.

Retrieve results

Once the job is completed, fetch results with GET /v1/bulk-lookup/{job_id}/results. Results are paginated. Page through them with limit and offset.

Submitting a job

Send your list of people in the JSON body. Each row needs a domain and at least one of first_name and last_name. To search by LinkedIn profile URL instead, send a linkedin_url on every row (see LinkedIn profile URLs).

curl --request POST \
  --url "https://api.orbisearch.com/v1/bulk-lookup" \
  --header "X-API-Key: YOUR_API_KEY" \
  --header "Content-Type: application/json" \
  --data '{
    "input": [
      {"first_name": "Jane",  "last_name": "Doe",   "domain": "acme.com"},
      {"first_name": "John",  "last_name": "Smith", "domain": "bigcorp.io"},
      {"first_name": "Priya", "last_name": "Patel", "domain": "studio.xyz"}
    ]
  }'

import requests

response = requests.post(
    "https://api.orbisearch.com/v1/bulk-lookup",
    json={
        "input": [
            {"first_name": "Jane",  "last_name": "Doe",   "domain": "acme.com"},
            {"first_name": "John",  "last_name": "Smith", "domain": "bigcorp.io"},
            {"first_name": "Priya", "last_name": "Patel", "domain": "studio.xyz"},
        ],
    },
    headers={"X-API-Key": "YOUR_API_KEY"},
)
job = response.json()
print(job["job_id"], job["total_rows"], "credits charged:", job["credits_consumed"])

const response = await fetch(
  "https://api.orbisearch.com/v1/bulk-lookup",
  {
    method: "POST",
    headers: {
      "X-API-Key": "YOUR_API_KEY",
      "Content-Type": "application/json",
    },
    body: JSON.stringify({
      input: [
        { first_name: "Jane",  last_name: "Doe",   domain: "acme.com" },
        { first_name: "John",  last_name: "Smith", domain: "bigcorp.io" },
        { first_name: "Priya", last_name: "Patel", domain: "studio.xyz" },
      ],
    }),
  }
);
const job = await response.json();
console.log(job.job_id, job.total_rows, "credits charged:", job.credits_consumed);

OrbiSearch responds with a job ID and the deduplicated row count:

{
  "job_id": "123e4567-e89b-12d3-a456-426614174000",
  "status": "submitted",
  "total_rows": 3,
  "credits_consumed": 3
}

OrbiSearch deduplicates the input array automatically (case-insensitive on first name + last name + domain, and on the profile for LinkedIn URLs, so two forms of the same profile URL count once). If your list has duplicates, you are only charged for the unique rows.

Checking job status

Poll GET /v1/bulk-lookup/{job_id} to track progress.

curl --request GET \
  --url "https://api.orbisearch.com/v1/bulk-lookup/123e4567-e89b-12d3-a456-426614174000" \
  --header "X-API-Key: YOUR_API_KEY"

status_response = requests.get(
    f"https://api.orbisearch.com/v1/bulk-lookup/{job_id}",
    headers={"X-API-Key": "YOUR_API_KEY"},
)
status = status_response.json()
print(status["status"], status["total_processed"], "/", status["total_rows"])

const statusRes = await fetch(
  `https://api.orbisearch.com/v1/bulk-lookup/${job_id}`,
  { headers: { "X-API-Key": "YOUR_API_KEY" } }
);
const status = await statusRes.json();
console.log(status.status, `${status.total_processed}/${status.total_rows}`);

While the job is running, the response looks like this:

{
  "job_id": "123e4567-e89b-12d3-a456-426614174000",
  "status": "running",
  "total_rows": 3,
  "total_processed": 2,
  "summary": {
    "total_found": 1,
    "total_not_found": 1
  },
  "created_at": "2026-04-26T06:30:00Z",
  "finished_at": null
}

status is running until every row has been processed, at which point it becomes completed and finished_at is populated. The summary object updates live as rows complete, so you can show progress to your end user before the job is fully done.

Retrieving results

Once status is completed, fetch the full results. Use limit and offset to page through them. The default limit is 50 and the maximum is 500.

curl --request GET \
  --url "https://api.orbisearch.com/v1/bulk-lookup/123e4567-e89b-12d3-a456-426614174000/results?limit=100&offset=0" \
  --header "X-API-Key: YOUR_API_KEY"

results_response = requests.get(
    f"https://api.orbisearch.com/v1/bulk-lookup/{job_id}/results",
    params={"limit": 100, "offset": 0},
    headers={"X-API-Key": "YOUR_API_KEY"},
)
data = results_response.json()
for row in data["results"]:
    if row["status"] == "safe":
        print(f"{row['first_name']} {row['last_name']} → {row['email']}")
    else:
        print(f"{row['first_name']} {row['last_name']} → not found")

const resultsRes = await fetch(
  `https://api.orbisearch.com/v1/bulk-lookup/${job_id}/results?limit=100&offset=0`,
  { headers: { "X-API-Key": "YOUR_API_KEY" } }
);
const data = await resultsRes.json();
for (const row of data.results) {
  if (row.status === "safe") {
    console.log(`${row.first_name} ${row.last_name} → ${row.email}`);
  } else {
    console.log(`${row.first_name} ${row.last_name} → not found`);
  }
}

Each row in results has the same shape as a single email finder response:

{
  "job_id": "123e4567-e89b-12d3-a456-426614174000",
  "total_rows": 3,
  "total_processed": 3,
  "limit": 100,
  "offset": 0,
  "results": [
    {
      "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
    },
    {
      "first_name": "John",
      "last_name": "Smith",
      "domain": "bigcorp.io",
      "email_domain": "bigcorp.io",
      "linkedin_url": null,
      "email": null,
      "status": "unknown",
      "substatus": "no_address_found",
      "explanation": "No deliverable address could be found for the given name at this domain.",
      "confidence": null,
      "full_name": null,
      "employer_name": null,
      "employer_linkedin_url": null,
      "all_emails": null,
      "email_provider": "Unknown",
      "mx_record": null,
      "is_domain_catch_all": null,
      "is_secure_email_gateway": false,
      "is_disposable": null,
      "is_role_account": null,
      "is_free": null,
      "credits_consumed": 1
    },
    {
      "first_name": "Priya",
      "last_name": "Patel",
      "domain": "studio.xyz",
      "email_domain": "studio.xyz",
      "linkedin_url": null,
      "email": "priya@studio.xyz",
      "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": "Microsoft Outlook",
      "mx_record": "studio-xyz.mail.protection.outlook.com",
      "is_domain_catch_all": false,
      "is_secure_email_gateway": false,
      "is_disposable": false,
      "is_role_account": false,
      "is_free": false,
      "credits_consumed": 1
    }
  ]
}

When email is null, OrbiSearch could not find a deliverable address for that person at that domain, so don’t send to them there.

LinkedIn profile URLs

A job can search by LinkedIn profile URL instead of a name and domain. Send a linkedin_url on every row:

{
  "input": [
    {"linkedin_url": "https://www.linkedin.com/in/jane-doe"},
    {"linkedin_url": "https://www.linkedin.com/in/john-smith"}
  ]
}

One job uses one kind of input: every row a linkedin_url, or every row a name and domain. A list that mixes the two is rejected with 422 before anything is charged, and the error names the first row of the other kind. To search both kinds of list, submit two jobs. What to expect for LinkedIn rows:

Results carry the same extra fields as a single search by LinkedIn URL: linkedin_url, full_name, employer_name, employer_linkedin_url, and all_emails. In a name and domain job these fields are null.
Substatuses: besides deliverable and no_address_found, a LinkedIn row can end as profile_not_found (a correctly formed profile URL that is not a valid profile, for example mistyped or no longer in use), no_current_employer (we couldn’t identify a current employer for this person) or no_company_website (the employer has no company website we could identify; if you know it, resubmit the row by name and domain). All three are charged.
Invalid URLs are not rejected. A row whose value isn’t a LinkedIn profile URL at all (for example a company page URL or plain text) is returned in the results with substatus: invalid_linkedin_url and credits_consumed: 0, and the rest of the job runs normally. It counts toward total_rows, but not toward the credits charged at submit.
temporarily_unavailable: in rare cases we can’t complete a row. It’s returned with this substatus, and you can resubmit it in a new job.

Pricing

Each unique row costs 1 credit, deducted upfront when you submit the job, whether it’s a LinkedIn URL or a name and domain. Every returned row is charged, except a row with substatus: invalid_linkedin_url, which is free. Refunds are issued only when OrbiSearch infrastructure cannot accept or process the submission itself. In that case the upfront charge is reversed and no job is created.

Limits and rate limits

Maximum 10,000 rows per submission. Split larger lists across multiple jobs.
This endpoint shares the 20 requests per second per account limit with the rest of the /v1/* API.

Complete example

Python

import time
import requests

API_KEY = "YOUR_API_KEY"
BASE_URL = "https://api.orbisearch.com"
HEADERS = {"X-API-Key": API_KEY, "Content-Type": "application/json"}

people = [
    {"first_name": "Jane",  "last_name": "Doe",   "domain": "acme.com"},
    {"first_name": "John",  "last_name": "Smith", "domain": "bigcorp.io"},
    {"first_name": "Priya", "last_name": "Patel", "domain": "studio.xyz"},
    # ... up to 10,000 rows
]

# 1. Submit
submit = requests.post(f"{BASE_URL}/v1/bulk-lookup", headers=HEADERS, json={"input": people})
submit.raise_for_status()
job = submit.json()
job_id = job["job_id"]
print(f"Submitted: {job_id} ({job['total_rows']} unique rows, {job['credits_consumed']} credits charged)")

# 2. Poll until complete
while True:
    status = requests.get(f"{BASE_URL}/v1/bulk-lookup/{job_id}", headers=HEADERS).json()
    print(f"  {status['status']}: {status['total_processed']}/{status['total_rows']}")
    if status["status"] == "completed":
        break
    time.sleep(15)

# 3. Page through results
offset = 0
while True:
    page = requests.get(
        f"{BASE_URL}/v1/bulk-lookup/{job_id}/results",
        params={"limit": 500, "offset": offset},
        headers=HEADERS,
    ).json()
    if not page["results"]:
        break
    for row in page["results"]:
        if row["status"] == "safe":
            print(f"{row['first_name']} {row['last_name']} → {row['email']}")
        else:
            print(f"{row['first_name']} {row['last_name']} → not found")
    offset += len(page["results"])

Get Started

Core Concepts

Guides

Find Work Emails in Bulk From LinkedIn URLs or Names and Domains

When to use the bulk email finder

How the bulk email finder works

Submitting a job

Checking job status

Retrieving results

LinkedIn profile URLs

Pricing

Limits and rate limits

Complete example

​When to use the bulk email finder

​How the bulk email finder works

​Submitting a job

​Checking job status

​Retrieving results

​LinkedIn profile URLs

​Pricing

​Limits and rate limits

​Complete example

When to use the bulk email finder

How the bulk email finder works

Submitting a job

Checking job status

Retrieving results

LinkedIn profile URLs

Pricing

Limits and rate limits

Complete example