# Hunter.io Email Finder, Verifier & Enrichment (`muhammadafzal/hunter-io-api-actor`) Actor

Find, verify, enrich, and analyze professional email data with Hunter.io's API for sales, lead generation, and agent workflows.

- **URL**: https://apify.com/muhammadafzal/hunter-io-api-actor.md
- **Developed by:** [Muhammad Afzal](https://apify.com/muhammadafzal) (community)
- **Categories:** Lead generation, MCP servers
- **Stats:** 1 total users, 0 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.00 / 1,000 hunter results

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.

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

## Hunter.io Email Finder & Enrichment API Actor

Run Hunter.io's read-only API from Apify to find professional email addresses, verify deliverability, enrich people and companies, resolve company names to domains, inspect email counts, or read account usage.

This Actor uses Hunter's first-party API with an API key you provide. It does not scrape hunter.io, automate a browser, bypass authentication, or provide a Hunter subscription. Hunter API credits and rate limits remain the responsibility of the Hunter account that owns the key.

### Supported operations

| Operation | Batch input | Output behavior |
| --- | --- | --- |
| `domainSearch` | `domains` | One row per Hunter email result, with type, confidence, role metadata, verification, and sources. |
| `emailFinder` | `contacts` | One row for each found person email; no row is fabricated when Hunter finds none. |
| `emailVerifier` | `emails` | One row per verification response, including status, score, MX/SMTP details in `payload`. |
| `domainFinder` | `companies` | One row per candidate domain returned by Hunter. This is a Hunter beta endpoint and may change. |
| `emailCount` | `domains` | One row per domain count response; totals and department breakdown remain in `payload`. |
| `emailEnrichment` | `emails` | One row per enriched person, including name, employment, location, and social handles in `payload`. |
| `companyEnrichment` | `domains` | One row per enriched company, including industry, location, site, and category data in `payload`. |
| `account` | none | One row containing account usage and plan information in `payload`. |

Hunter's current API documentation describes Domain Search, Email Finder, and Email Verifier as its main endpoints, with enrichment and account endpoints also available. See [Hunter's API Reference](https://hunter.io/api-documentation).

### Input example

```json
{
  "apiKey": "YOUR_HUNTER_API_KEY",
  "operation": "emailFinder",
  "contacts": [
    {
      "domain": "stripe.com",
      "firstName": "Patrick",
      "lastName": "Collison"
    }
  ],
  "includeRawData": true
}
```

For a domain search:

```json
{
  "apiKey": "YOUR_HUNTER_API_KEY",
  "operation": "domainSearch",
  "domains": ["stripe.com", "hunter.io"],
  "limit": 25,
  "type": "personal",
  "decisionMaker": true
}
```

The input schema marks `apiKey` as secret. Do not place API keys in README examples used for real runs, dataset fields, or custom logs.

### Output

Each dataset item has the same top-level shape across operations:

```json
{
  "operation": "emailFinder",
  "requestKey": "{\"domain\":\"stripe.com\",\"firstName\":\"Patrick\",\"lastName\":\"Collison\"}",
  "email": "patrick@stripe.com",
  "domain": "stripe.com",
  "company": "Stripe",
  "firstName": "Patrick",
  "lastName": "Collison",
  "fullName": "Patrick Collison",
  "position": "Cofounder",
  "seniority": null,
  "department": null,
  "type": null,
  "decisionMaker": null,
  "confidence": 97,
  "status": "valid",
  "sourceCount": 1,
  "sources": [{ "domain": "stripe.com", "uri": "https://stripe.com/about" }],
  "payload": {},
  "fetchedAt": "2026-08-02T12:00:00.000Z"
}
```

Set `includeRawData` to `false` when you only need the normalized columns and want smaller dataset items. The run summary is written to the `SUMMARY` key-value record; it includes request counts, empty responses, warnings, API errors, and completion timestamps. A dataset/output reference is written to `OUTPUT`.

### Reliability and limits

- Up to 100 batch values per run.
- Requests are sequential and have a configurable delay (`requestDelayMs`, default 100 ms).
- Transient `429` and `5xx` responses are retried with bounded exponential backoff; authentication, validation, legal, and not-found responses are reported in the summary without fabricated dataset records.
- Hunter's Email Verifier can return HTTP 202 while verification is in progress. The Actor polls up to five times before preserving the response as a warning.
- A valid query with zero matches is reported as an empty result with a warning. This is different from a failed API request.

### Apify pricing

This Actor uses Apify pay-per-event pricing. The event prices below include the Actor's platform usage:

| Event | Price | When it is charged |
| --- | ---: | --- |
| Actor start | $0.00005 | Once per run, scaled by Actor memory with a one-event minimum |
| Hunter result | $0.003 | For each normalized result written to the default dataset |

Hunter may separately charge the API key's account according to Hunter's endpoint and plan rules. Runs that return no normalized results incur only the Actor-start event.

### Responsible use

Use the API only for lawful, permissioned business workflows. Respect Hunter's terms, applicable privacy and anti-spam laws, suppression requests, and the rights of people whose data is returned. Do not use this Actor to process claimed or restricted personal data, send unsolicited messages, or infer sensitive personal attributes.

# Actor input Schema

## `apiKey` (type: `string`):

Use this when calling Hunter.io. Enter the API key from your Hunter dashboard, for example 'your-hunter-api-key'. It is sent only to api.hunter.io and is never written to logs or output.

## `operation` (type: `string`):

Use this to choose one read-only Hunter.io endpoint. The batch field for the selected operation must also be supplied. Defaults to domainSearch.

## `domains` (type: `array`):

Use this for domainSearch, emailCount, or companyEnrichment. Enter domains such as 'stripe.com', or company names when the selected endpoint supports company lookup. One value per line; maximum 100 values.

## `emails` (type: `array`):

Use this for emailVerifier or emailEnrichment. Enter one professional email address per line, for example 'patrick@stripe.com'. Maximum 100 values.

## `companies` (type: `array`):

Use this for domainFinder. Enter company names with at least 3 characters, such as 'Stripe' or 'Y Combinator'. Maximum 100 values.

## `contacts` (type: `array`):

Use this for emailFinder. Each object needs a domain, company, or linkedinHandle plus firstName and lastName, fullName, or linkedinHandle. Example: {"domain":"stripe.com","firstName":"Patrick","lastName":"Collison"}. Maximum 100 contacts.

## `limit` (type: `integer`):

Use this to limit results for domainSearch or domainFinder. Domain Search accepts 1-100; Domain Finder accepts 1-10. Defaults to 10 for domainSearch and 5 for domainFinder.

## `offset` (type: `integer`):

Use this with domainSearch to skip previously returned emails for pagination. Defaults to 0 and is capped at 100000.

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

Use this with domainSearch or emailCount to keep only personal or generic addresses. Leave unset for both.

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

Use this with domainSearch to filter by a Hunter seniority value such as 'executive', 'senior', 'middle', or 'junior'. Leave unset for all.

## `department` (type: `string`):

Use this with domainSearch to filter by a Hunter department such as 'sales', 'marketing', 'executive', or 'it'. Leave unset for all.

## `decisionMaker` (type: `boolean`):

Use this with domainSearch to return only likely decision makers when true or only non-decision makers when false. Leave unset for all.

## `aggregations` (type: `boolean`):

Use this with domainSearch to include department, decision-maker, personal, and generic counts in each record's payload. Defaults to false.

## `perfectMatch` (type: `boolean`):

Use this with domainFinder to request only high-similarity company-domain matches. Defaults to false.

## `includeRawData` (type: `boolean`):

Use this to retain Hunter's endpoint-specific data under payload. Set false to omit payload for a smaller dataset. Defaults to true.

## `requestDelayMs` (type: `integer`):

Use this to pace batches and stay below Hunter rate limits. Enter 0-10000 milliseconds. Defaults to 100.

## Actor input object example

```json
{
  "operation": "domainSearch",
  "limit": 10,
  "offset": 0,
  "aggregations": false,
  "perfectMatch": false,
  "includeRawData": true,
  "requestDelayMs": 100
}
```

# Actor output Schema

## `dataset` (type: `string`):

Normalized Hunter.io records written by the Actor.

## `summary` (type: `string`):

Operation, request counts, warnings, API errors, and completion metadata.

## `output` (type: `string`):

Dataset and summary references for API consumers.

# 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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("muhammadafzal/hunter-io-api-actor").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 = {}

# Run the Actor and wait for it to finish
run = client.actor("muhammadafzal/hunter-io-api-actor").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 '{}' |
apify call muhammadafzal/hunter-io-api-actor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,muhammadafzal/hunter-io-api-actor"
        }
    }
}

```

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/MnCEgvbVebtZB5fcd/builds/mkC9Jw7An4a5Jlue9/openapi.json