Hunter.io Email Finder & Enrichment API Actor

Free-plan limit: Apify free-plan users receive at most 5 delivered dataset results per run. Paid and agentic-payment runs may process the configured batch. Hunter API usage still follows the supplied Hunter account's credits and limits.

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 are accepted for paid and agentic-payment runs. Apify free-plan users receive at most 5 delivered dataset records per run; high-cardinality domainSearch and domainFinder operations are reduced to one API request with a result limit of 5 so a single response cannot exceed the free cap.
• 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

Current Apify event prices and platform-usage treatment are listed in the dedicated Pricing section below.

This Actor uses Apify pay-per-event pricing. Current event prices, platform-usage treatment, and any scheduled changes are listed in the dedicated Pricing section below.

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.

Use cases

• Build public prospect lists and qualify organizations or professionals before responsible outreach.
• Run a one-off research job and export the structured result as JSON, CSV, Excel, XML, or RSS from Apify.
• Schedule the same input to monitor changes over time and send completed datasets to a webhook or integration.
• Feed schema-shaped records into a database, spreadsheet, BI tool, or AI workflow with the source URL retained for verification.

Pricing

This Actor uses pay-per-event pricing. These are the current Apify Store event prices:

Event	Price (USD)	When it is charged
apify-default-dataset-item	$0.003	Hunter result — Charged for each normalized Hunter.io result written to the default dataset.
apify-actor-start	$0.00005	Actor Start — Charged when the Actor starts running. Number of events charged depends on Actor memory (one event per GB, minimum one event). — Charged once per run.

Platform usage is currently billed separately by Apify for this Actor run. A scheduled change takes effect on 2026-09-30; from then, platform usage is included alongside the event prices above, with no separate per-run platform-usage fee passed to users.

This covers Apify platform usage for this Actor run. Other Apify products or usage outside this Actor run may still follow your account plan.

Scheduled event prices from 2026-09-30:

Event	Price (USD)	When it is charged
apify-default-dataset-item	FREE: $0.009; BRONZE: $0.009; SILVER: $0.009; GOLD: $0.007; PLATINUM: $0.007; DIAMOND: $0.007	Hunter result — Charged for each normalized Hunter.io result written to the default dataset.
apify-actor-start	$0.005	Actor Start — Charged when the Actor starts running. Number of events charged depends on Actor memory (one event per GB, minimum one event). — Charged once per run.