# Email Enrichment API - Saad (`amr-mando/email-enrichment-api`) Actor

Turn a name + company domain, a LinkedIn profile URL, or a company domain + job title into a verified work email. Every result carries a deliverability verdict.

- **URL**: https://apify.com/amr-mando/email-enrichment-api.md
- **Developed by:** [Mando](https://apify.com/amr-mando) (community)
- **Categories:** Lead generation, AI, Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$0.01 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Email Enrichment API

Turns a person or a company into a verified work email.

Every result carries a deliverability verdict, so coverage and accuracy can be measured
separately rather than combined into a single hit-rate figure.

### What it accepts

A list of leads. Each lead may take any one of three shapes, and they can be mixed freely in a
single call — every row is routed on its own.

| Input | Returns |
|---|---|
| First name, last name, company domain | That person's work email |
| LinkedIn profile URL | That person's work email |
| Company domain and a job title | The person on that domain whose title is closest, with their email |

Supplying a company name instead of a domain is supported; the domain is resolved automatically.

### What it returns

One row per submitted lead, in the order submitted:

| Field | Meaning |
|---|---|
| `email` | The work email, or empty if none was found |
| `email_status` | `valid`, `risky`, `invalid`, `unknown` or `not_found` |
| `first_name`, `last_name`, `job_title` | The person the email belongs to |
| `domain`, `company` | The company it resolved to |
| `mail_provider` | The mail platform behind the domain |
| `catch_all_domain` | Whether the domain accepts any address |
| `linkedin_url` | The profile, and whether it was supplied or found |
| `input_mode` | Which shape the row was routed as |

`valid` means the mailbox was confirmed to accept mail. `risky` generally means the domain is
catch-all or sits behind a gateway that accepts everything, so no service can confirm the
individual mailbox. `invalid` means the address was actively rejected.

### Access

Operated by Amrico. Access is arranged directly — contact the operator for an evaluation.

# Actor input Schema

## `leads` (type: `array`):

An array of leads. Each object may use any ONE of the three supported shapes — they can be mixed freely in a single call, each row is routed on its own:

1. NAME + COMPANY DOMAIN — {"first\_name": "Aaron", "last\_name": "Levie", "domain": "box.com"}
2. LINKEDIN URL — {"linkedin\_url": "https://www.linkedin.com/in/dylanfield"}
3. COMPANY DOMAIN + JOB TITLE — {"domain": "datadoghq.com", "job\_title": "VP of Engineering"}

Aliases are accepted for every field (firstName/first, companyDomain/website, linkedinUrl/profile\_url, title/role). Send "company" instead of "domain" and the domain is resolved for you. Anything you send back is echoed in the result under "input".

## `defaultJobTitle` (type: `string`):

Used only for shape 3 rows that give a domain but no job\_title. The engine returns the person on that domain whose real title is closest to this one.

## `seniority` (type: `string`):

Which band to search inside. "auto" reads it off the job title you asked for, which is almost always right — set it explicitly only to force a band.

## `maxLeadsPerCompany` (type: `integer`):

How many people to pull per domain before keeping the closest title match. Higher = better title fit, slower run.

## `findLinkedInUrl` (type: `boolean`):

For shape 1 rows. When the profile URL is not supplied, find it from the name + company first. Materially raises the hit rate. Turn off for the fastest possible run.

## `resolveDomains` (type: `boolean`):

When a lead gives a company name but no domain, find the domain first. Applies to all three shapes.

## `includeSiteScrape` (type: `boolean`):

ON by default, for maximum coverage. When no personal mailbox is confirmed, return a real email published on the company's own website. IMPORTANT: what a company publishes is usually a shared inbox (info@, support@, billing@) rather than the individual you asked for - on a hard test list this accounted for about a quarter of the results. TURN THIS OFF if you need the exact person and an accurate per-person hit rate. Always tagged email\_source="scraped" so you can filter or score it separately.

## `recoverUnverified` (type: `boolean`):

After the main pass, take every row that came back risky, invalid or empty and return a DIFFERENT decision maker at the same company instead. This replaces the person: new name, new title, new profile. Use it when you want a reachable contact at the account and do not mind who it is. Do not use it when you need the specific person you asked for. Every replaced row comes back with recovered=true. Off by default.

## `includePersonalFallback` (type: `boolean`):

ON by default. Last resort for people the company domain could not confirm: tests common personal providers (Gmail, Outlook, Yahoo, iCloud). A hit confirms the mailbox exists, not that it belongs to this specific person, so it is tagged email\_source="personal-guess". Turn it off if you only want addresses on the company's own domain.

## Actor input object example

```json
{
  "leads": [
    {
      "first_name": "Aaron",
      "last_name": "Levie",
      "domain": "box.com"
    },
    {
      "linkedin_url": "https://www.linkedin.com/in/dylanfield"
    },
    {
      "domain": "datadoghq.com",
      "job_title": "VP of Engineering"
    }
  ],
  "defaultJobTitle": "Head of Operations",
  "seniority": "auto",
  "maxLeadsPerCompany": 3,
  "findLinkedInUrl": true,
  "resolveDomains": true,
  "includeSiteScrape": true,
  "recoverUnverified": false,
  "includePersonalFallback": true
}
```

# Actor output Schema

## `results` (type: `string`):

No description

## `csvOutput` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "leads": [
        {
            "first_name": "Aaron",
            "last_name": "Levie",
            "domain": "box.com"
        },
        {
            "linkedin_url": "https://www.linkedin.com/in/dylanfield"
        },
        {
            "domain": "datadoghq.com",
            "job_title": "VP of Engineering"
        }
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("amr-mando/email-enrichment-api").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "leads": [
        {
            "first_name": "Aaron",
            "last_name": "Levie",
            "domain": "box.com",
        },
        { "linkedin_url": "https://www.linkedin.com/in/dylanfield" },
        {
            "domain": "datadoghq.com",
            "job_title": "VP of Engineering",
        },
    ] }

# Run the Actor and wait for it to finish
run = client.actor("amr-mando/email-enrichment-api").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "leads": [
    {
      "first_name": "Aaron",
      "last_name": "Levie",
      "domain": "box.com"
    },
    {
      "linkedin_url": "https://www.linkedin.com/in/dylanfield"
    },
    {
      "domain": "datadoghq.com",
      "job_title": "VP of Engineering"
    }
  ]
}' |
apify call amr-mando/email-enrichment-api --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,amr-mando/email-enrichment-api"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/7HAn3YVQ7oKoabR8j/builds/AsRkiDkY6pUZhhJ65/openapi.json