---
title: "Search Business Email by Name"
method: POST
path: "/search_business_email_by_name"
tags: ["Search"]
---

# Search Business Email by Name

`POST /search_business_email_by_name`

## Request

- Base URL: `https://api.moltsets.com/api/v1/tools`
- URL: `https://api.moltsets.com/api/v1/tools/search_business_email_by_name`
- Auth: HTTP bearer

The Business Email Finder API finds a person's valid work email address from just their name and company domain.

It runs a LinkedIn profile search and an email lookup in a single call, and returns the email address along with the matched LinkedIn profile URL. Pass a full name or separate `first_name` and `last_name` fields, and provide the company as a domain, for example `acme.com`. URLs are normalised automatically, and tokens are only charged when an email is found.

**Use this endpoint to:**
- Find a prospect's work email before outreach
- Fill in missing email fields on a lead list
- Enrich CRM records with verified contact emails

**Fair Use Policy:**
This API is subject to our <a href="https://moltsets.com/fair-use-policy-search/" target="_blank" rel="noopener">Fair Use Policy for Search</a>.

**Outcomes:**
A lookup that finds nothing is not an error. It returns HTTP `200` with `status: "not_found"`, empty or null `results`, and the usual `metadata` — and costs no tokens, though it still counts as one request against your Fair Use requests limit. Read `status`, not the HTTP code, to tell a hit from a miss. The API's only `404` is an unknown or retired tool name.

## Headers

- `User-Agent` string, required

## Request body

- object
  - `name` string: Full name (e.g. 'John Smith') — parsed into first and last name automatically.
  - `first_name` string: First name (used if `name` is not provided).
  - `last_name` string: Last name (used if `name` is not provided).
  - `company` string: Company domain (e.g. 'acme.com') or URL (e.g. 'https://acme.com') — normalized to domain.
  - `company_domain` string: Alias for `company` — company domain or URL.

## Response `200`

Success

## Other responses

- `401`: Unauthorized
- `402`: Payment Required — insufficient tokens
- `403`: Forbidden — missing `User-Agent` header, tool not on the plan, or account inactive
- `422`: Invalid Input — malformed body, or a parameter is missing, malformed, or outside its allowed values
- `429`: Too Many Requests — rate limit or Fair Use window exhausted
- `500`: Internal Server Error — the call could not complete. Usually the endpoint is temporarily unavailable, but an oversized request can also cause it. Retry with a smaller request first; the MoltSets team is alerted automatically.

---

[API](https://skmtc.dev/moltsets/apis/moltsets-api.md) - [All operations](https://skmtc.dev/moltsets/apis/moltsets-api/llms.txt) - [OpenAPI document](https://skmtc.dev/moltsets/apis/moltsets-api/revisions/b116df68bd90?raw)