Email Finding API
Email Finding Icypeas API
通过持久化的请求生命周期,根据人员和公司查找工作邮箱。
POST/v1/run/email_finding.icypeas
请求数
-
30d
调用方式
发出你的第一个请求
import os, requests res = requests.post( "https://api.getanyapi.com/v1/run/email_finding.icypeas", headers={"Authorization": f"Bearer {os.environ['ANYAPI_KEY']}"}, json={ "domainOrCompany": "" }, ) print(res.json())
示例响应
{
"data": {
"certainty": "example",
"createdUtc": 12.5,
"email": "alex@example.com",
"emails": [
{
"certainty": "example",
"email": "alex@example.com",
"mxProvider": "a1b2c3d4",
"mxRecords": [
"example"
]
}
],
"firstname": "Alex",
"fullname": "Alex Rivera",
"gender": "example",
"lastname": "Rivera",
"linkedinUrl": "https://example.com/page",
"modifiedUtc": 12.5,
"mxProvider": "a1b2c3d4",
"mxRecords": [
"example"
],
"phones": null,
"saasServices": null,
"scanId": "a1b2c3d4",
"scanName": "Example title",
"scanOrder": 1,
"scanStatus": "active",
"scanUser": "example"
},
"found": true,
"reason": "not_found"
}响应类型定义
interface EmailFindingIcypeasResponse {
data: {
certainty?: string;
createdUtc?: number;
email: string;
emails?: {
certainty?: string;
email?: string;
mxProvider?: string;
mxRecords?: string[];
}[];
firstname?: string;
fullname?: string;
gender?: string;
lastname?: string;
linkedinUrl?: string;
modifiedUtc?: number;
mxProvider?: string;
mxRecords?: string[];
phones?: any;
saasServices?: any;
scanId?: string;
scanName?: string;
scanOrder?: number;
scanStatus?: string;
scanUser?: string;
} | null;
found: boolean;
reason?: "not_found";
}完整的参数与响应参考:这个接口的每个字段、类型和示例。
参考
请求、响应与价格
最近验证于 2026-09-29 · 可用率和延迟按 30d 统计POST /v1/run/email_finding.icypeas
curl -X POST https://api.getanyapi.com/v1/run/email_finding.icypeas \
-H "Authorization: Bearer $ANYAPI_KEY" \
-H "Content-Type: application/json" \
-d '{"domainOrCompany":"apollo.io","firstname":"Tim","lastname":"Zheng"}'| 字段 | 类型 | 示例值 |
|---|---|---|
| 请求体 | ||
| domainOrCompany | string | "apollo.io" |
| firstname | string | "Tim" |
| lastname | string | "Zheng" |
| 响应 | ||
| data | object | The matched person and email, or null when nothing was found. |
| data.certainty | string | Confidence label for the best matching address, e.g. ultra_sure. |
| data.createdUtc | number | UTC epoch timestamp in seconds (Unix time). Multiply by 1000 for a JS Date in milliseconds. |
| data.email | string | Best matching email address. |
| data.emails | object[] | Every candidate address found for the person, best first. The top-level email is the first entry. |
| data.emails[].certainty | string | Confidence label for this address, e.g. ultra_sure. |
| data.emails[].email | string | Candidate email address. |
| data.emails[].mxProvider | string | Mail provider behind this address's domain. |
| data.emails[].mxRecords | string[] | Mail exchange records for this address's domain. |
| data.firstname | string | Matched first name. |
| data.fullname | string | Matched full name. |
| data.gender | string | Gender recorded for the matched person. Absent when the source does not know it. |
| data.lastname | string | Matched last name. |
| data.linkedinUrl | string | LinkedIn profile URL for the matched person, when the source has one. |
| data.modifiedUtc | number | UTC epoch timestamp in seconds (Unix time). Multiply by 1000 for a JS Date in milliseconds. |
| data.mxProvider | string | Mail provider behind the domain, e.g. google. |
| data.mxRecords | string[] | Mail exchange records for the domain. |
| data.phones | any | Phone numbers Icypeas returned alongside the address. Deliberately untyped: the field is empty in every response we have captured, so the value passes through without a shape guarantee. |
| data.saasServices | any | SaaS services Icypeas associates with the person. Deliberately untyped: the field is empty in every response we have captured, so the value passes through without a shape guarantee. |
| data.scanId | string | Icypeas' identifier for the search that produced this result. |
| data.scanName | string | Icypeas' internal label for the kind of search that ran, e.g. __icypeas__individual. |
| data.scanOrder | integer | Position of this result inside the Icypeas search batch. It is 0 for the single-person search this SKU runs. |
| data.scanStatus | string | Icypeas' terminal status for the search, FOUND or NOT_FOUND. It duplicates the envelope's found flag. |
| data.scanUser | string | Icypeas account that ran the search. |
| found | boolean | False when no email was found for the person. |
| 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.0168 |
| 价格(/千次请求) | USD | US$16.80 |
常见问题
关于 Email Finding Icypeas API
AnyAPI 的 Email Finding Icypeas API 只需一次 POST 请求 /v1/run/email_finding.icypeas,就以统一格式的 JSON 返回 Email Finding 数据。通过持久化的请求生命周期,根据人员和公司查找工作邮箱。无论哪个数据源提供服务,AnyAPI 都返回同一套统一的 schema。费用:每千次请求 US$16.80 起,以美元计价,无需订阅,也没有每月最低消费。
费用:每千次请求 US$16.80 起,以美元计价,无需订阅,也没有每月最低消费。你只需为一个美元钱包充值,每次调用从中扣费。部分由钱包付费的失败请求会产生处理费用,我们按成本原价转嫁,不加价;错误响应会显示收取的金额。
通过持久化的请求生命周期,根据人员和公司查找工作邮箱。响应是统一格式的 JSON,外层结构与每个 AnyAPI 接口相同,所以解析另一个接口只需换一个 URL,别的都不用改。