Email Finding API
Email Finding Hunter 计数 API
统计某个公司域名有多少联系人,分为个人邮箱和通用邮箱,并按部门和职级细分。先以每 1,000 次请求 $1 的价格评估一个域名,再决定是否按联系人付费。
POST/v1/run/email_finding.hunter_count
可用率
100.00%
30d · 3 次调用
请求数
3
30d · 按周,近 12 周
响应时间
1.4s
中位数 · 30d
试一试
发出你的第一个请求
示例响应
免费运行只返回前 3 条结果。为密钥充值即可获得完整响应。
{
"data": {
"departmentCounts": {
"administrative": 42,
"communication": 42,
"consulting": 42,
"design": 42,
"education": 42,
"executive": 42,
"finance": 42,
"health": 42,
"hr": 42,
"it": 42,
"legal": 42,
"management": 29,
"marketing": 42,
"operation": 13,
"operations": 13,
"procurement": 42,
"product": 42,
"research": 42,
"sales": 42,
"support": 42
},
"domain": "example.com",
"genericEmails": 42,
"personalEmails": 42,
"seniorityCounts": {
"executive": 42,
"junior": 42,
"senior": 42
},
"total": 12500,
"type": "general"
},
"found": true,
"reason": "not_found"
}响应类型定义
interface EmailFindingHunterCountResponse {
data: {
departmentCounts?: {
administrative?: number;
communication?: number;
consulting?: number;
design?: number;
education?: number;
executive?: number;
finance?: number;
health?: number;
hr?: number;
it?: number;
legal?: number;
management?: number;
marketing?: number;
operation?: number;
operations?: number;
procurement?: number;
product?: number;
research?: number;
sales?: number;
support?: number;
};
domain: string;
genericEmails?: number;
personalEmails?: number;
seniorityCounts?: {
executive?: number;
junior?: number;
senior?: number;
};
total: number;
type?: string;
} | null;
found: boolean;
reason?: "not_found";
}完整的参数与响应参考:这个接口的每个字段、类型和示例。
参考
请求、响应与价格
最近验证于 2026-09-29 · 可用率和延迟按 30d 统计POST /v1/run/email_finding.hunter_count
curl -X POST https://api.getanyapi.com/v1/run/email_finding.hunter_count \
-H "Authorization: Bearer $ANYAPI_KEY" \
-H "Content-Type: application/json" \
-d '{"domain":"stripe.com"}'| 字段 | 类型 | 示例值 |
|---|---|---|
| 请求体 | ||
| domain | string | "stripe.com"公司域名,不含协议或路径,例如 stripe.com。 |
| type | enum | 只统计属于具名人员的个人邮箱,或只统计 info@ 和 support@ 这类通用邮箱。 |
| 响应 | ||
| data | object | |
| data.departmentCounts | object | Contacts per department. |
| data.departmentCounts.administrative | integer | Contacts in the administrative department. |
| data.departmentCounts.communication | integer | Contacts in the communication department. |
| data.departmentCounts.consulting | integer | Contacts in the consulting department. |
| data.departmentCounts.design | integer | Contacts in the design department. |
| data.departmentCounts.education | integer | Contacts in the education department. |
| data.departmentCounts.executive | integer | Contacts in the executive department. |
| data.departmentCounts.finance | integer | Contacts in the finance department. |
| data.departmentCounts.health | integer | Contacts in the health department. |
| data.departmentCounts.hr | integer | Contacts in the HR department. |
| data.departmentCounts.it | integer | Contacts in the IT department. |
| data.departmentCounts.legal | integer | Contacts in the legal department. |
| data.departmentCounts.management | integer | Contacts in the management department. |
| data.departmentCounts.marketing | integer | Contacts in the marketing department. |
| data.departmentCounts.operation | integer | Contacts Hunter files under its separate operation department. |
| data.departmentCounts.operations | integer | Contacts in the operations department. |
| data.departmentCounts.procurement | integer | Contacts in the procurement department. |
| data.departmentCounts.product | integer | Contacts in the product department. |
| data.departmentCounts.research | integer | Contacts in the research department. |
| data.departmentCounts.sales | integer | Contacts in the sales department. |
| data.departmentCounts.support | integer | Contacts in the support department. |
| data.domain | string | The company domain the counts describe. |
| data.genericEmails | integer | Contacts that are a shared inbox such as info@ or support@. |
| data.personalEmails | integer | Contacts that are a named person's mailbox. |
| data.seniorityCounts | object | Contacts per seniority level. |
| data.seniorityCounts.executive | integer | Contacts at executive level. |
| data.seniorityCounts.junior | integer | Contacts at junior level. |
| data.seniorityCounts.senior | integer | Contacts at senior level. |
| data.total | integer | Contacts known for the domain. |
| data.type | string | Mailbox type the counts are limited to when the request filtered by type: personal or generic. Absent when the counts cover both. |
| found | boolean | False when the domain has no counted contacts. |
| 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. |
| 价格 | ||
| 每次请求价格 | USD | US$0.001 |
| 价格(/千次请求) | USD | US$1.00 |
常见问题
关于 Email Finding Hunter 计数 API
AnyAPI 的 Email Finding Hunter 计数 API 只需一次 POST 请求 /v1/run/email_finding.hunter_count,就以统一格式的 JSON 返回 Email Finding 数据。统计某个公司域名有多少联系人,分为个人邮箱和通用邮箱,并按部门和职级细分。先以每 1,000 次请求 $1 的价格评估一个域名,再决定是否按联系人付费。无论哪个数据源提供服务,AnyAPI 都返回同一套统一的 schema。费用:每千次请求 US$1 起,以美元计价,无需订阅,也没有每月最低消费。过去 30 天,通过 AnyAPI 发起的 Email Finding Hunter 计数 API 调用中有 100.0% 成功,响应时间中位数为 1.4 秒,共测量 3 次调用。
费用:每千次请求 US$1 起,以美元计价,无需订阅,也没有每月最低消费。你只需为一个美元钱包充值,每次调用从中扣费。部分由钱包付费的失败请求会产生处理费用,我们按成本原价转嫁,不加价;错误响应会显示收取的金额。
统计某个公司域名有多少联系人,分为个人邮箱和通用邮箱,并按部门和职级细分。先以每 1,000 次请求 $1 的价格评估一个域名,再决定是否按联系人付费。响应是统一格式的 JSON,外层结构与每个 AnyAPI 接口相同,所以解析另一个接口只需换一个 URL,别的都不用改。
过去 30 天,通过 AnyAPI 发起的 Email Finding Hunter 计数 API 调用中有 100.0% 成功,响应时间中位数为 1.4 秒,共测量 3 次调用。这些是 AnyAPI 对经过网关的流量的自有测量,持续重新计算,并非公开承诺的服务等级目标。