Hunter logo

Find Email Using Name and Company Domain (Hunter.io)

Hunter → Find Email Using Name and Company Domain (Hunter.io)

POST/v1/hunter-find-email
texau__hunter-find-emailenrichment
Run in Studio →Open in MCP
cURL · api.texau.app
84ms
POST/v1/hunter-find-email
{
  "domain": "https://acme.com",
  "first_name": "Jane",
  "last_name": "Doe"
}
200 Accepted
{
  "ok": true,
  "data": {
    "email": "[email protected]",
    "score": 92,
    "position": "sample",
    "company": "sample",
    "verification_status": "valid"
  }
}

Finds a professional email address using a person's full name and company domain via Hunter.io.

Install

Add find email using name and company domain (hunter.io) to your MCP client.

Drop this into claude_desktop_config.json (or your client's equivalent) and the tool shows up in any chat.

claude_desktop_config.json
{
  "mcpServers": {
    "texau": {
      "command": "npx",
      "args": ["-y", "@texau/mcp-server"],
      "env": { "TEXAU_API_KEY": "..." }
    }
  }
}

Tool name: texau__hunter-find-email

When to use this.

The "hunter-find-email" action allows users to efficiently locate email addresses based on a contact's name and their associated company domain using Hunter.io's powerful email verification tools. This action requires three key input parameters: the company domain, the first name, and the last name of the individual. Upon execution, it returns essential output fields including the email address, a confidence score indicating the reliability of the found email, the job title of the contact, the company name, and the verification status of the email. This action is particularly useful for sales and marketing professionals seeking to enrich their lead databases, improve outreach efforts, and enhance networking opportunities by ensuring accurate contact information. Categorized under enrichment, "hunter-find-email" streamlines the process of connecting with potential clients or partners by providing verified email addresses.

Try it

Run a sample request.

The response is a deterministic, cached example. No live call, no credits used.

Find Email Using Name and Company Domain (Hunter.io)

Try it

Company domain

First name of the contact

Last name of the contact

Response is cached — no live API call.

Response

Output schema.

Every field returned in `data`. Click rows to expand nested objects.

FieldType
  • email
    Email
    text
  • score
    Score
    number
  • position
    Position
    text
  • company
    Company
    text
  • verification_status
    Verification Status
    text

Integrate

Copy-pasteable snippets.

Real endpoint: https://v3-api.texau.com/api/v1/hunter-find-email. Auth: x-api-key.

cURL · api.texau.app
84ms
POST/v1/hunter-find-email
curl -X POST 'https://v3-api.texau.com/api/v1/hunter-find-email' \
  -H 'x-api-key: $TEXAU_API_KEY' \
  -H 'content-type: application/json' \
  -d '{"domain":"https://acme.com","first_name":"Jane","last_name":"Doe"}'
200 Accepted
{
  "ok": true,
  "data": {
    "email": "[email protected]",
    "score": 92,
    "position": "sample",
    "company": "sample",
    "verification_status": "valid"
  }
}

Compose

How this fits a workflow.

The next 2 actions most operators chain after this one.

Find Email Using Name and Company Domain (Hunter.io)→Find Mobile Number by LinkedIn URL (Hunter.io)→Find Mobile Number Using Email (Hunter.io)

Output

Results land in a TexAu table.

Sample rows below.

Real result preview coming soon.

InputStatusScore
[email protected]valid96
[email protected]risky54
[email protected]invalid12

Workflow

A real example.

Trigger → find email using name and company domain (hunter.io) → enrich → push to your CRM. ~80 ms operator effort, the rest runs in the background.

Step 1TriggerNew row, webhook, or schedule.
Step 2Find Email Using Name and Company Domain (Hunter.io)Hunter action runs.
Step 3EnrichWaterfall fills missing fields.
Step 4Push to CRMHubSpot / Salesforce / Pipedrive.

Built for

Who runs this.

GTM EngineerRevOpsAgency

Reliability

Rate limits & reliability.

  • Per-minute limit450 / min
  • Per-day limit10,000 / day
  • RetriesAutomatic w/ backoff
  • ModeSync

Errors

HTTP status codes.

What each response means and what to do about it.

CodeCauseFix
200 OKAction ran. Data in `data`.Read response.
400 Bad RequestMissing or malformed input.Validate against the input schema.
401 UnauthorizedMissing or invalid `x-api-key`.Re-issue from /api-platform.
403 ForbiddenWorkspace lacks plan tier.Upgrade or contact sales.
404 Not FoundAction key not recognized.Verify the slug.
429 Rate LimitedPer-minute or per-day cap hit.Backoff; reduce concurrency.
500 Server ErrorUnexpected TexAu issue.Retry with backoff.
502 Bad GatewayUpstream provider 5xx.Retry; we surface root cause.
504 TimeoutUpstream slower than maxLatency.Switch to `isAsync` polling.

Pricing

What it costs to run.

Standard tier

Pricing tier on /pricing. Per-action credit cost is private.

Related

More Hunter actions.

FAQ.

  • Is this real-time?

    Yes. Synchronous actions return in ~1–4 s. Long-running work uses async polling (see status 504 → switch to async).

  • Do I get charged on failure?

    No. Verified failures cost zero credits. Provider miss / 5xx / timeout cascade to the next provider in the waterfall when applicable.

  • Does it work with Claude / Cursor via MCP?

    Yes. Add the texau MCP server to your client config, then call `texau__hunter-...` directly.

  • What CRMs can I push results to?

    HubSpot, Salesforce, Pipedrive, Zoho, and GoHighLevel are bidirectional. Smartlead, Instantly, Lemlist, HeyReach, Apollo Sequences, and Reply.io for outbound.

Run Find Email Using Name and Company Domain (Hunter.io) in 60 seconds.

Pull your API key, paste the cURL, ship to your CRM.

Start free →Read the API docs