Email Finding API

Email Finding Quickenrich API

根据 LinkedIn 主页，或根据公司域名加姓名查找工作邮箱。对小型和本地企业覆盖最好，对大型科技公司覆盖较少。

POST/v1/run/email_finding.quickenrich
可用率
100.00%
30d · 17 次调用
请求数
17
30d · 按周，近 12 周
响应时间
1.1s
中位数 · 30d

价格

一个价格，以美元计

试一试

发出你的第一个请求

打开于
获取免费密钥
示例响应
免费运行只返回前 3 条结果。为密钥充值即可获得完整响应。
{
  "data": {
    "address": "123 Main St",
    "city": "San Francisco",
    "companyDomain": "example.com",
    "companyEmployeeCount": "Acme Inc",
    "companyIndustry": "Acme Inc",
    "companyLinkedinUrl": "https://example.com/page",
    "companyName": "Acme Inc",
    "companyPhone": "+1 555-0142",
    "companyRevenue": "Acme Inc",
    "country": "US",
    "email": "alex@example.com",
    "emailDomain": "alex@example.com",
    "emailVerifiedUtc": 12.5,
    "firstName": "Alex",
    "lastName": "Rivera",
    "linkedinUrl": "https://example.com/page",
    "phone": "+1 555-0142",
    "phoneType": "+1 555-0142",
    "postalCode": "94107",
    "region": "CA",
    "title": "Example title"
  },
  "found": true,
  "reason": "not_found"
}
响应类型定义
interface EmailFindingQuickenrichResponse {
  data: {
    address?: string;
    city?: string;
    companyDomain?: string;
    companyEmployeeCount?: string;
    companyIndustry?: string;
    companyLinkedinUrl?: string;
    companyName?: string;
    companyPhone?: string;
    companyRevenue?: string;
    country?: string;
    email: string;
    emailDomain?: string;
    emailVerifiedUtc?: number;
    firstName?: string;
    lastName?: string;
    linkedinUrl?: string;
    phone?: string;
    phoneType?: string;
    postalCode?: string;
    region?: string;
    title?: string;
  } | null;
  found: boolean;
  reason?: "not_found";
}

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

参考

请求、响应与价格

最近验证于 2026-09-29 · 可用率和延迟按 30d 统计
POST /v1/run/email_finding.quickenrich
curl -X POST https://api.getanyapi.com/v1/run/email_finding.quickenrich \
  -H "Authorization: Bearer $ANYAPI_KEY" \
  -H "Content-Type: application/json" \
  -d '{"companyDomain":"southmemphisfence.com","firstName":"Warren","lastName":"Price"}'
字段类型示例值
请求体
companyDomainstring"southmemphisfence.com"公司网站域名，由上游标准化（example.com 或 https://example.com 都可以）。
firstNamestring"Warren"人员的名字。
lastNamestring"Price"人员的姓氏。
linkedinUrlstringLinkedIn 主页 URL。提供此项，或提供 companyDomain 以及 firstName 和 lastName。
响应
dataobjectNormalized record, or null when the request matched nothing.
data.addressstringStreet address on the employer record.
data.citystringCity on the employer record.
data.companyDomainstringEmployer website domain.
data.companyEmployeeCountstringEmployer headcount band, e.g. "20 - 99". Upstream band vocabulary; "Not Available" means the band is unknown.
data.companyIndustrystringEmployer industry label.
data.companyLinkedinUrlstringEmployer LinkedIn company URL.
data.companyNamestringEmployer name.
data.companyPhonestringEmployer main phone line.
data.companyRevenuestringEmployer revenue band, e.g. "1 - 2.5 Million". Upstream band vocabulary; "Not Available" means the band is unknown.
data.countrystringISO 3166-1 alpha-2 country code on the employer record.
data.emailstringWork email address.
data.emailDomainstringDomain the work email resolves to.
data.emailVerifiedUtcnumberUTC epoch timestamp in seconds (Unix time). Multiply by 1000 for a JS Date in milliseconds.
data.firstNamestringPerson's first name.
data.lastNamestringPerson's last name.
data.linkedinUrlstringPerson's LinkedIn profile URL.
data.phonestringDirect business phone line held for the person. Mostly desk lines; read phoneType before treating it as a mobile.
data.phoneTypestringLine type reported upstream, e.g. "mobile" or "landline".
data.postalCodestringPostal code on the employer record.
data.regionstringState or region code on the employer record.
data.titlestringPerson's job title.
foundbooleanFalse when no email matched, including when the person was located but no address is held for them.
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.0072
价格（/千次请求）USDUS$7.20

常见问题

关于 Email Finding Quickenrich API

AnyAPI 的 Email Finding Quickenrich API 只需一次 POST 请求 /v1/run/email_finding.quickenrich，就以统一格式的 JSON 返回 Email Finding 数据。根据 LinkedIn 主页，或根据公司域名加姓名查找工作邮箱。对小型和本地企业覆盖最好，对大型科技公司覆盖较少。无论哪个数据源提供服务，AnyAPI 都返回同一套统一的 schema。费用：每千次请求 US$7.20 起，以美元计价，无需订阅，也没有每月最低消费。过去 30 天，通过 AnyAPI 发起的 Email Finding Quickenrich API 调用中有 100.0% 成功，响应时间中位数为 1.1 秒，共测量 17 次调用。

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

根据 LinkedIn 主页，或根据公司域名加姓名查找工作邮箱。对小型和本地企业覆盖最好，对大型科技公司覆盖较少。响应是统一格式的 JSON，外层结构与每个 AnyAPI 接口相同，所以解析另一个接口只需换一个 URL，别的都不用改。

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

Email Finding 的其他接口

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