Email Finding API

Email Finding Hunter 域名 API

查找某个公司域名下的具名联系人及其工作邮箱,可按职位、职级或部门筛选。按返回的联系人计价,因此 limit 就是成本控制手段。

US$25.00/千次请求,按请求付费,无需订阅。

meridianfreight.com - Hunter
app.hunter.io/search
Search
61 emails found{first}.{last}
NameEmailConfidence
N

Nora Whitfield

VP of Logistics

nora.whitfield@meridianfreight.com94%
API 返回的内容emails[0]
{
"email": "nora.whitfield@meridianfreight.com",
"confidence": 94,
"firstName": "Nora",
"lastName": "Whitfield",
"position": "VP of Logistics",
"seniority": "executive",
"linkedinUrl": "https://www.linkedin.com/in/norawhitfield",
"phone": "+1 415-555-0142",
... 还有 9 个字段
}
可用率
100.00%
30d · 2,405 次调用
请求数
2,436
30d · 按周,近 12 周
响应时间
1.0s
中位数 · 30d

价格与服务商

Email Finding Hunter 域名 API 价格:一个 API,2 个可互换的服务商

最便宜的服务商优先响应。如果它失败,下一个会在同一次调用中接手。

你需支付
US$250.00
US$25.00/千次请求,只为实际用量付费。没有月度套餐。
有了 US$0.10 的初始余额,你的前 4 次请求免费。

调用方式

一个请求获取 Email Finding Hunter 域名

import os, requests

res = requests.post(
    "https://api.getanyapi.com/v1/run/email_finding.hunter_domain",
    headers={"Authorization": f"Bearer {os.environ['ANYAPI_KEY']}"},
    json={
        "domain": "stripe.com",
        "limit": 2,
        "type": "personal"
    },
)
print(res.json())
打开于
获取免费密钥
示例响应

这个示例展示了 34 个字段中的 31 个。查看全部字段

{
  "found": true,
  "data": {
    "domain": "meridianfreight.com",
    "linkedDomains": [],
    "organization": "Meridian Freight Co.",
    "emailPattern": "{first}.{last}",
    "acceptAll": false,
    "disposable": false,
    "webmail": false,
    "totalCount": 61,
    "emails": [
      {
        "email": "nora.whitfield@meridianfreight.com",
        "confidence": 94,
        "firstName": "Nora",
        "lastName": "Whitfield",
        "position": "VP of Logistics",
        "seniority": "executive",
        "linkedinUrl": "https://www.linkedin.com/in/norawhitfield",
        "phone": "+1 415-555-0142"
      },
      {
        "email": "derek.holt@meridianfreight.com",
        "type": "personal",
        "sourceType": "generated",
        "confidence": 78,
        "firstName": "Derek",
        "lastName": "Holt",
        "position": "Account Manager",
        "seniority": "senior",
        "department": "sales",
        "decisionMaker": false,
        "linkedinUrl": "https://www.linkedin.com/in/derekholt",
        "verificationStatus": "accept_all",
        "verifiedUtc": 1747958400,
        "sources": [
          {
            "domain": "linkedin.com",
            "url": "https://www.linkedin.com/in/derekholt",
            "stillOnPage": true,
            "extractedUtc": 1744243200,
            "lastSeenUtc": 1747958400
          }
        ]
      }
    ]
  }
}

完整的参数与响应参考:这个接口的每个字段、类型和示例。

参考

一个请求,一种响应结构。

你发送的每个字段和收到的每个字段,都附有真实示例。

最近验证于 2026-11-14 · 可用率和延迟按 30d 统计

请求体

JSON,POST 到这个接口。

  • domainstring

    meridianfreight.com

    公司域名,不含协议或路径,例如 stripe.com。

  • departmentenum

    限定为一个部门。

  • jobTitlestring

    要匹配的一个职位关键词,例如 editor。只支持单个关键词:不支持逗号分隔的列表,否则只有最后一项生效。

  • limitinteger

    2

    本次响应最多返回的联系人数。每个返回的联系人都会扣费,因此这就是成本控制手段。

  • offsetinteger

    本页开始前要跳过的联系人数。

  • requiredFieldenum

    只返回带有此字段的联系人。

  • seniorityenum

    限定为一个职级。

  • typeenum

    personal

    限定为属于具名人员的个人邮箱,或 info@ 和 support@ 这类通用邮箱。

你发送。 一个简短的 JSON 请求体。显示的值只是示例,请换成你自己的。

响应

JSON,每个字段一个示例值。

datadata
  • acceptAllboolean

    false

    True when the mail server accepts any address at this domain, so an address cannot be verified by delivery.

  • disposableboolean

    false

    True when the domain belongs to a disposable-email service.

  • domainstring

    meridianfreight.com

    The company domain the contacts belong to.

  • emailPatternstring

    {first}.{last}

    Address pattern the company uses, e.g. {first}{last}.

  • linkedDomainsany

    Other domains Hunter has linked to this company. Deliberately untyped: the field is empty in every response we have captured, so the value passes through without a shape guarantee.

  • organizationstring

    Meridian Freight Co.

    Company name registered against the domain.

  • totalCountinteger

    61

    Contacts matching the filters across the whole domain, of which this response returns at most limit.

  • webmailboolean

    false

    True when the domain is a webmail provider rather than a company.

each emaildata.emails[]

Contacts returned by this page, one per billed result.

  • confidenceinteger

    94

    Upstream confidence in the address, 0 to 100.

  • decisionMakerboolean

    True when the contact is judged a decision maker.

  • departmentstring

    Department the contact works in.

  • emailstring

    nora.whitfield@meridianfreight.com

    The work email address.

  • firstNamestring

    Nora

    Contact's first name.

  • lastNamestring

    Whitfield

    Contact's last name.

  • linkedinUrlstring

    https://www.linkedin.com/in/norawhitfield

    Contact's LinkedIn profile URL.

  • phonestring

    +1 415-555-0142

    Contact's phone number.

  • positionstring

    VP of Logistics

    Contact's job title.

  • positionRawstring

    Contact's job title exactly as written on the source page, before it was cleaned up.

  • senioritystring

    executive

    Seniority level: junior, senior or executive.

  • sourceTypestring

    How the address was obtained: found when it was seen on a public page, generated when it was inferred from the company's address pattern.

  • twitterstring

    Contact's Twitter/X handle or profile URL, exactly as the source recorded it.

  • typestring

    personal for a named person's mailbox, generic for a shared inbox.

  • verificationStatusstring

    Deliverability verdict recorded for the address.

  • verifiedUtcnumber

    UTC epoch timestamp in seconds (Unix time). Multiply by 1000 for a JS Date in milliseconds.

each sourcedata.emails[].sources[]

Public pages the address was found on.

  • domainstring

    Domain of the page the address was found on.

  • extractedUtcnumber

    UTC epoch timestamp in seconds (Unix time). Multiply by 1000 for a JS Date in milliseconds.

  • lastSeenUtcnumber

    UTC epoch timestamp in seconds (Unix time). Multiply by 1000 for a JS Date in milliseconds.

  • stillOnPageboolean

    True when the address was still present at the last check.

  • urlstring

    URL of the page the address was found on.

top level
  • foundboolean

    true

    False when the domain yielded no contacts for the requested filters.

  • reason"not_found"

    Present only when `found` is false, and says why there is no result. `not_found`: the source states the target does not exist, or returned nothing for it. A `found: false` answer is a successful call, not an error, and `costUsd` is what it actually cost.

你收到。 字段有名称、有类型,无论哪个数据源响应,结构都一样。

常见问题

关于 Email Finding Hunter 域名 API

AnyAPI 的 Email Finding Hunter 域名 API 只需一次 POST 请求 /v1/run/email_finding.hunter_domain,就以统一格式的 JSON 返回 Email Finding 数据。查找某个公司域名下的具名联系人及其工作邮箱,可按职位、职级或部门筛选。按返回的联系人计价,因此 limit 就是成本控制手段。AnyAPI 会在 2 个数据源之间路由每个请求,某个数据源失败时自动切换。费用:每千次请求 US$25 起,以美元计价,无需订阅,也没有每月最低消费。过去 30 天,通过 AnyAPI 发起的 Email Finding Hunter 域名 API 调用中有 100.0% 成功,响应时间中位数为 1.0 秒,共测量 2,405 次调用。

费用:每千次请求 US$25 起,以美元计价,无需订阅,也没有每月最低消费。你只需为一个美元钱包充值,每次调用从中扣费。部分由钱包付费的失败请求会产生处理费用,我们按成本原价转嫁,不加价;错误响应会显示收取的金额。

查找某个公司域名下的具名联系人及其工作邮箱,可按职位、职级或部门筛选。按返回的联系人计价,因此 limit 就是成本控制手段。响应是统一格式的 JSON,外层结构与每个 AnyAPI 接口相同,所以解析另一个接口只需换一个 URL,别的都不用改。

过去 30 天,通过 AnyAPI 发起的 Email Finding Hunter 域名 API 调用中有 100.0% 成功,响应时间中位数为 1.0 秒,共测量 2,405 次调用。这些是 AnyAPI 对经过网关的流量的自有测量,持续重新计算,并非公开承诺的服务等级目标。

可以。新的 AnyAPI 账户自带 US$0.10 免费余额,无需绑卡,足够调用 4 次 Email Finding Hunter 域名,每次 US$0.025。

AnyAPI 会在同一个请求中依次尝试它的 2 个数据源,从最便宜的开始,所以一个数据源宕机不会让你的调用失败。

向 https://api.getanyapi.com/v1/run/email_finding.hunter_domain 发送 POST 请求,在 “Authorization: Bearer” 请求头中放入你的 AnyAPI 密钥,并以 JSON 请求体传入参数。同一个密钥和同一个钱包适用于所有 AnyAPI 接口。

不需要。你向一个预付费的 AnyAPI 余额充值美元,每个请求从中扣费。没有月度套餐,也没有最低消费,同一个余额可用于所有 AnyAPI 接口。

有。TypeScript 用 npm 安装 @getanyapi/sdk,Python 用 pip 安装 getanyapi。两者都用同一个密钥调用所有 AnyAPI 接口,任何 HTTP 客户端也都可以。

可以。智能体可以连接 https://api.getanyapi.com/mcp 上的 AnyAPI MCP 服务器,或者向 https://api.getanyapi.com/agent/signup 发送一次无需认证的 POST 来创建自己的免费试用密钥,再通过 HTTP 调用这个接口。