mail

GET /v1/mail/services/{mailServiceId}/deliverability

SPF, DKIM and DMARC state for a domain that already has email.

所有 mail 端点

身份验证

请将 API 密钥作为 bearer 令牌发送。该密钥必须具有 mail.view 权限;缺少该权限的密钥将被拒绝并返回 403 状态码,而非 404。

此端点不需要组织 ID。您的密钥已用于识别其所属的组织,且响应范围也仅限于该组织。

免费试用

将尖括号中的内容替换为您自己的值,并将键占位符替换为您仪表板中的一个键。

curl -X GET https://api.zinndigital.com/v1/mail/services/{mailServiceId}/deliverability \
  -H "Authorization: Bearer zdk_live_…"

已登录?您仪表板中的 API 控制台会自动填入您真实的组织 ID 和您自己的密钥,并针对实时 API 运行请求,以便您查看实际的响应。 在 API 控制台中打开此端点

详细信息

Whether this domain's mail is set up to be **delivered** - the question a customer asks when their messages land in spam. ⛔ A different question from `/preflight`, which asks what setting mail up here would destroy; both read the same underlying report so a preview and the fix cannot disagree. `fixable` is false when the apex MX belongs to somebody else or the zone cannot be read, because a one-click apply would then either destroy working mail or write blind. Requires `mail.view`.

参数

名称类型必填内容简介
mailServiceId (path)UuidEmail service ID (UUIDv7).

响应

名称类型必填内容简介
domainstring
healthybooleanAll three mechanisms present and ours - nothing to publish.
spf_okboolean
dkim_okboolean
dmarc_okboolean
fixablebooleanWhether a one-click apply is offered. **False** over a foreign apex MX or an unreadable zone - the panel shows the reason instead of a button.
needs_confirmationbooleanTrue when applying would replace published records, so `confirm` is required.
existing_apex_mxstring[]
foreign_mxstring[]Apex MX targets that are not ours - the reason a fix is refused.
foreign_spf_includesstring[]
would_deletestring[]Records an apply would remove or replace, as `NAME TYPE VALUE`. Listed verbatim rather than counted: a customer must not be able to destroy mail records without seeing which one…
zone_unreadableboolean
reasonstringCustomer-grade English. Never a driver message.
warningsstring[]

此端点可能返回的错误

401 · 403 · 404 · 429