随着用户越来越多地依赖电子邮件进行各种目的,如客户获取、营销活动和账户管理,确保电子邮件地址的准确性和有效性变得至关重要。电子邮件完整性API旨在满足这一需求,提供全面的电子邮件验证和有效性检查功能。
本质上,电子邮件完整性API对电子邮件地址执行一系列检查和验证,以确保其准确性和有效性。这些检查包括语法验证、域名验证和邮箱验证。语法验证检查电子邮件地址的结构,以确保其遵循标准格式(例如,用户名@域名.com)。域名验证通过查询DNS记录检查电子邮件地址的域名部分的存在,而邮箱验证检查与电子邮件地址关联的邮箱是否存在并可访问。
通过执行这些检查,电子邮件完整性API帮助公司识别并删除其数据库中无效或不准确的电子邮件地址。这不仅提高了客户数据的整体质量,还帮助避免了如邮件退回、垃圾邮件投诉和低电子邮件投递率等问题。
使用电子邮件完整性API的主要优势之一是其能够检测和标记一次性或临时电子邮件地址。这些地址通常由临时电子邮件服务提供,用户通常用于短期目的,例如注册在线服务或访问受限内容。尽管在某些情况下,这些电子邮件地址可能服务于合法用途,但它们通常与垃圾邮件、欺诈和滥用相关。通过识别和过滤一次性电子邮件地址,API帮助公司维护一个干净和可靠的电子邮件数据库,从而提高其电子邮件营销活动和沟通工作的有效性。
总之,电子邮件完整性API是帮助公司提高电子邮件数据库的准确性和有效性的有价值工具。通过执行全面的检查和验证、检测一次性电子邮件地址以及提供实时验证和集成功能等附加功能,API帮助用户维护干净和可靠的电子邮件数据库,提高电子邮件投递率,增强整体沟通效果。
它将接收参数并向您提供JSON。
除了API调用次数,没有其他限制。
要使用此端点,您必须输入1个或多个电子邮件
验证 - 端点功能
| 对象 | 描述 |
|---|---|
请求体 |
[必需] Json |
{"duplicates":[],"results":[{"email":"[email protected]","domain":"gmail.com","classification":"Risky","status":["Attempt_Rejected","Delivery failed; the reason is similar to \"rejected\"."],"result":{"syntaxValidation":{"passed":true,"message":"The address is valid according to syntax rules."},"domainValidation":{"passed":true,"message":"gmail.com is verified","suggestion":""},"isDisposableEmail":{"passed":false,"message":"Disposable validation passed for gmail.com"},"mxRecords":{"exists":true,"records":[{"exchange":"alt3.gmail-smtp-in.l.google.com","priority":30},{"exchange":"alt4.gmail-smtp-in.l.google.com","priority":40},{"exchange":"alt1.gmail-smtp-in.l.google.com","priority":10},{"exchange":"alt2.gmail-smtp-in.l.google.com","priority":20},{"exchange":"gmail-smtp-in.l.google.com","priority":5}],"message":"gmail.com domain has valid DNS records."},"roleAccount":{"passed":false,"role":"","message":"The email address is not a recognized role account"},"ispSpecific":{"passed":true,"message":"Following the syntactic rules of the target mail exchanger for the gmail.com domain, the address is considered syntactically valid."},"freeEmail":{"passed":true,"message":"This email address is associated with a well-known free email provider"},"smtpPing":{"passed":true,"message":"SMTP ping passed"}}},{"email":"[email protected]","domain":"gmail.com","classification":"Risky","status":["Attempt_Rejected","Delivery failed; the reason is similar to \"rejected\"."],"result":{"syntaxValidation":{"passed":true,"message":"The address is valid according to syntax rules."},"domainValidation":{"passed":true,"message":"gmail.com is verified","suggestion":""},"isDisposableEmail":{"passed":false,"message":"Disposable validation passed for gmail.com"},"mxRecords":{"exists":true,"records":[{"exchange":"alt1.gmail-smtp-in.l.google.com","priority":10},{"exchange":"gmail-smtp-in.l.google.com","priority":5},{"exchange":"alt4.gmail-smtp-in.l.google.com","priority":40},{"exchange":"alt3.gmail-smtp-in.l.google.com","priority":30},{"exchange":"alt2.gmail-smtp-in.l.google.com","priority":20}],"message":"gmail.com domain has valid DNS records."},"roleAccount":{"passed":false,"role":"","message":"The email address is not a recognized role account"},"ispSpecific":{"passed":true,"message":"Following the syntactic rules of the target mail exchanger for the gmail.com domain, the address is considered syntactically valid."},"freeEmail":{"passed":true,"message":"This email address is associated with a well-known free email provider"},"smtpPing":{"passed":true,"message":"SMTP ping passed"}}},{"email":"[email protected]","domain":"gmail.com","classification":"Risky","status":["Attempt_Rejected","Delivery failed; the reason is similar to \"rejected\"."],"result":{"syntaxValidation":{"passed":true,"message":"The address is valid according to syntax rules."},"domainValidation":{"passed":true,"message":"gmail.com is verified","suggestion":""},"isDisposableEmail":{"passed":false,"message":"Disposable validation passed for gmail.com"},"mxRecords":{"exists":true,"records":[{"exchange":"alt1.gmail-smtp-in.l.google.com","priority":10},{"exchange":"gmail-smtp-in.l.google.com","priority":5},{"exchange":"alt3.gmail-smtp-in.l.google.com","priority":30},{"exchange":"alt2.gmail-smtp-in.l.google.com","priority":20},{"exchange":"alt4.gmail-smtp-in.l.google.com","priority":40}],"message":"gmail.com domain has valid DNS records."},"roleAccount":{"passed":false,"role":"","message":"The email address is not a recognized role account"},"ispSpecific":{"passed":true,"message":"Following the syntactic rules of the target mail exchanger for the gmail.com domain, the address is considered syntactically valid."},"freeEmail":{"passed":true,"message":"This email address is associated with a well-known free email provider"},"smtpPing":{"passed":true,"message":"SMTP ping passed"}}},{"email":"[email protected]","domain":"gmail.com","classification":"Risky","status":["Attempt_Rejected","Delivery failed; the reason is similar to \"rejected\"."],"result":{"syntaxValidation":{"passed":true,"message":"The address is valid according to syntax rules."},"domainValidation":{"passed":true,"message":"gmail.com is verified","suggestion":""},"isDisposableEmail":{"passed":false,"message":"Disposable validation passed for gmail.com"},"mxRecords":{"exists":true,"records":[{"exchange":"alt2.gmail-smtp-in.l.google.com","priority":20},{"exchange":"gmail-smtp-in.l.google.com","priority":5},{"exchange":"alt1.gmail-smtp-in.l.google.com","priority":10},{"exchange":"alt4.gmail-smtp-in.l.google.com","priority":40},{"exchange":"alt3.gmail-smtp-in.l.google.com","priority":30}],"message":"gmail.com domain has valid DNS records."},"roleAccount":{"passed":false,"role":"","message":"The email address is not a recognized role account"},"ispSpecific":{"passed":true,"message":"Following the syntactic rules of the target mail exchanger for the gmail.com domain, the address is considered syntactically valid."},"freeEmail":{"passed":true,"message":"This email address is associated with a well-known free email provider"},"smtpPing":{"passed":true,"message":"SMTP ping passed"}}}]}
curl --location --request POST 'https://zylalabs.com/api/3542/email+integrity+api/3886/validation' --header 'Authorization: Bearer YOUR_API_KEY'
--data-raw '{
"emails": [
"[email protected]",
"[email protected]",
"[email protected]",
"[email protected]"
]
}'
| 标头 | 描述 |
|---|---|
授权
|
[必需] 应为 Bearer access_key. 订阅后,请查看上方的"您的 API 访问密钥"。 |
无长期承诺。随时升级、降级或取消。 免费试用包括最多 50 个请求。
要使用此API,用户必须指明电子邮件以获取有关它们是否有效的电子邮件的信息
电子邮件完整性API旨在通过提供全面的电子邮件验证、核实和完整性检查来确保电子邮件通信的准确性、可靠性和安全性
有不同的计划以满足各种口味,包括针对少量请求的免费试用,但您的速率受限以避免对服务的滥用
Zyla提供了几乎所有编程语言的多种集成方法。您可以根据需要使用这些代码与您的项目集成
验证端点返回一个包含提供的电子邮件地址有效性详细信息的 JSON 对象。这包括语法验证、域名验证、临时电子邮件状态和邮箱可访问性等字段
响应中的关键字段包括“电子邮件”“域名”“分类”“状态”和详细的验证结果,如“语法验证”“域名验证”和“是否为临时邮箱”,这些提供了有关电子邮件有效性的见解
响应数据结构为一个 JSON 对象,包含一个结果数组。每个结果包含每个电子邮件的特定验证细节,包括验证状态和消息,便于数据的轻松解读
验证端点提供了关于语法正确性、域名存在、邮箱可访问性,以及电子邮件是否为一次性邮箱或角色账户的信息,帮助用户全面评估电子邮件的有效性
用户可以在向验证端点的POST请求中输入一个或多个电子邮件地址作为参数 每个电子邮件地址将单独验证并在响应中返回
数据准确性通过多重验证检查得以保持,包括语法验证、域名验证的DNS查询和邮箱检查,确保处理的每个电子邮件地址都能获得可靠的结果
典型的用例包括用户注册验证 新闻通讯订阅验证 联系表单提交 账户验证和密码恢复过程 提升数据质量和沟通效果
用户可以分析返回的数据,以筛选出无效或临时电子邮件,提高他们的电子邮件列表并提升投递率 详细的验证结果可以根据每封电子邮件的分类和状态采取针对性的措施
服务级别:
100%
响应时间:
841ms
服务级别:
100%
响应时间:
57ms
服务级别:
100%
响应时间:
55ms
服务级别:
100%
响应时间:
1,541ms
服务级别:
100%
响应时间:
342ms
服务级别:
100%
响应时间:
755ms
服务级别:
100%
响应时间:
309ms
服务级别:
100%
响应时间:
315ms
服务级别:
100%
响应时间:
1,417ms
服务级别:
100%
响应时间:
316ms
服务级别:
100%
响应时间:
2,069ms
服务级别:
100%
响应时间:
2,938ms
服务级别:
100%
响应时间:
3,823ms
服务级别:
100%
响应时间:
1,815ms
服务级别:
100%
响应时间:
2,373ms
服务级别:
100%
响应时间:
534ms
服务级别:
100%
响应时间:
4,391ms
服务级别:
100%
响应时间:
5,980ms
服务级别:
100%
响应时间:
44ms
服务级别:
100%
响应时间:
1,793ms