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.

Input example

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

For a domain search:

{
  "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:

{
  "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.