Email Finding API

Email Finding Hunter 域名 API

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

POST/v1/run/email_finding.hunter_domain
可用率
99.05%
30d · 317 次调用
请求数
317
30d · 按周，近 12 周
响应时间
1.5s
中位数 · 30d

服务商网络

按流量排序的服务商

调用方式

发出你的第一个请求

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": ""
    },
)
print(res.json())
打开于
获取免费密钥
示例响应
{
  "data": {
    "acceptAll": true,
    "disposable": true,
    "domain": "example.com",
    "emailPattern": "alex@example.com",
    "emails": [
      {
        "confidence": 1024,
        "decisionMaker": true,
        "department": "example",
        "email": "alex@example.com",
        "firstName": "Alex",
        "lastName": "Rivera",
        "linkedinUrl": "https://example.com/page",
        "phone": "+1 555-0142",
        "position": "example",
        "positionRaw": "example",
        "seniority": "example",
        "sourceType": "https://example.com/page",
        "sources": [
          {
            "domain": "example.com",
            "extractedUtc": 12.5,
            "lastSeenUtc": 12.5,
            "stillOnPage": true,
            "url": "https://example.com/page"
          }
        ],
        "twitter": "example",
        "type": "general",
        "verificationStatus": "active",
        "verifiedUtc": 12.5
      }
    ],
    "linkedDomains": null,
    "organization": "Acme Inc",
    "totalCount": 12500,
    "webmail": true
  },
  "found": true,
  "reason": "not_found"
}
响应类型定义
interface EmailFindingHunterDomainResponse {
  data: {
    acceptAll?: boolean;
    disposable?: boolean;
    domain: string;
    emailPattern?: string;
    emails: {
      confidence?: number;
      decisionMaker?: boolean;
      department?: string;
      email: string;
      firstName?: string;
      lastName?: string;
      linkedinUrl?: string;
      phone?: string;
      position?: string;
      positionRaw?: string;
      seniority?: string;
      sourceType?: string;
      sources?: {
        domain: string;
        extractedUtc?: number;
        lastSeenUtc?: number;
        stillOnPage?: boolean;
        url?: string;
      }[];
      twitter?: string;
      type?: string;
      verificationStatus?: string;
      verifiedUtc?: number;
    }[];
    linkedDomains?: any;
    organization?: string;
    totalCount: number;
    webmail?: boolean;
  } | null;
  found: boolean;
  reason?: "not_found";
}

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

参考

请求、响应与价格

最近验证于 2026-09-29 · 可用率和延迟按 30d 统计
POST /v1/run/email_finding.hunter_domain
curl -X POST https://api.getanyapi.com/v1/run/email_finding.hunter_domain \
  -H "Authorization: Bearer $ANYAPI_KEY" \
  -H "Content-Type: application/json" \
  -d '{"domain":"stripe.com","limit":2,"type":"personal"}'
字段类型示例值
请求体
domainstring"stripe.com"公司域名，不含协议或路径，例如 stripe.com。
departmentenum限定为一个部门。
jobTitlestring要匹配的一个职位关键词，例如 editor。只支持单个关键词：不支持逗号分隔的列表，否则只有最后一项生效。
limitinteger2本次响应最多返回的联系人数。每个返回的联系人都会扣费，因此这就是成本控制手段。
offsetinteger本页开始前要跳过的联系人数。
requiredFieldenum只返回带有此字段的联系人。
seniorityenum限定为一个职级。
typeenum"personal"限定为属于具名人员的个人邮箱，或 info@ 和 support@ 这类通用邮箱。
响应
dataobject
data.acceptAllbooleanTrue when the mail server accepts any address at this domain, so an address cannot be verified by delivery.
data.disposablebooleanTrue when the domain belongs to a disposable-email service.
data.domainstringThe company domain the contacts belong to.
data.emailPatternstringAddress pattern the company uses, e.g. {first}{last}.
data.emailsobject[]Contacts returned by this page, one per billed result.
data.emails[].confidenceintegerUpstream confidence in the address, 0 to 100.
data.emails[].decisionMakerbooleanTrue when the contact is judged a decision maker.
data.emails[].departmentstringDepartment the contact works in.
data.emails[].emailstringThe work email address.
data.emails[].firstNamestringContact's first name.
data.emails[].lastNamestringContact's last name.
data.emails[].linkedinUrlstringContact's LinkedIn profile URL.
data.emails[].phonestringContact's phone number.
data.emails[].positionstringContact's job title.
data.emails[].positionRawstringContact's job title exactly as written on the source page, before it was cleaned up.
data.emails[].senioritystringSeniority level: junior, senior or executive.
data.emails[].sourceTypestringHow the address was obtained: found when it was seen on a public page, generated when it was inferred from the company's address pattern.
data.emails[].sourcesobject[]Public pages the address was found on.
data.emails[].sources[].domainstringDomain of the page the address was found on.
data.emails[].sources[].extractedUtcnumberUTC epoch timestamp in seconds (Unix time). Multiply by 1000 for a JS Date in milliseconds.
data.emails[].sources[].lastSeenUtcnumberUTC epoch timestamp in seconds (Unix time). Multiply by 1000 for a JS Date in milliseconds.
data.emails[].sources[].stillOnPagebooleanTrue when the address was still present at the last check.
data.emails[].sources[].urlstringURL of the page the address was found on.
data.emails[].twitterstringContact's Twitter/X handle or profile URL, exactly as the source recorded it.
data.emails[].typestringpersonal for a named person's mailbox, generic for a shared inbox.
data.emails[].verificationStatusstringDeliverability verdict recorded for the address.
data.emails[].verifiedUtcnumberUTC epoch timestamp in seconds (Unix time). Multiply by 1000 for a JS Date in milliseconds.
data.linkedDomainsanyOther 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.
data.organizationstringCompany name registered against the domain.
data.totalCountintegerContacts matching the filters across the whole domain, of which this response returns at most limit.
data.webmailbooleanTrue when the domain is a webmail provider rather than a company.
foundbooleanFalse 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.
价格
每次请求价格USDUS$0.025
价格（/千次请求）USDUS$25.00

常见问题

关于 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 调用中有 99.1% 成功，响应时间中位数为 1.5 秒，共测量 317 次调用。

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

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

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

Email Finding 的其他接口

Dropleads/千次请求 US$31.20 起Hunter 计数/千次请求 US$1.00 起Icypeas/千次请求 US$16.80 起Quickenrich/千次请求 US$7.20 起Zerobounce/千次请求 US$655.20 起Zerobounce 域名/千次请求 US$655.20 起