mail

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

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

Tüm mail uç noktaları

Tüm geliştirici belgeleri

Kimlik Doğrulama

Bearer token olarak bir API anahtarı gönderin. Anahtar mail.view iznine sahip olmalıdır; bu izne sahip olmayan bir anahtar 404 ile değil, 403 ile reddedilir.

Bu uç nokta hiçbir organizasyon kimliği almaz. Anahtarınız zaten ait olduğu organizasyonu tanımlar ve yanıt bu organizasyonla sınırlandırılır.

Dene

Köşeli parantez içindeki her şeyi kendi değerlerinizle ve anahtar yer tutucusunu panonuzdan bir anahtarla değiştirin.

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

Oturum açtınız mı? Panonuzdaki API konsolu, gerçek organizasyon kimliğinizi ve kendi anahtarınızı otomatik olarak doldurur ve isteği canlı API üzerinde çalıştırarak gerçek yanıtı görmenizi sağlar. Bu uç noktayı API konsolunda açın

Ayrıntılar

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.

Parametreler

AdTürZorunluNe olduğu
mailServiceId (path)UuidEvetEmail service ID (UUIDv7).

Yanıt

AdTürZorunluNe olduğu
domainstringEvet
healthybooleanEvetAll three mechanisms present and ours - nothing to publish.
spf_okbooleanEvet
dkim_okbooleanEvet
dmarc_okbooleanEvet
fixablebooleanEvetWhether 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_confirmationbooleanEvetTrue when applying would replace published records, so confirm is required.
existing_apex_mxstring[]Evet
foreign_mxstring[]EvetApex MX targets that are not ours - the reason a fix is refused.
foreign_spf_includesstring[]Evet
would_deletestring[]EvetRecords 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 ones…
zone_unreadablebooleanEvet
reasonstringEvetCustomer-grade English. Never a driver message.
warningsstring[]Evet
live_mxstring[]EvetThe domain's MX hosts as PUBLIC DNS answers them right now (W43-09) - not our record of the zone. Empty when the domain publishes no MX, or when it could not be read (see…
mx_readablebooleanEvetFalse when the public MX lookup failed. A failed lookup is never read as "action needed".
mx_okbooleanEvetEvery live MX host is one this preset publishes, and there is at least one.
action_neededbooleanEvetThe customer's OWN DNS must change: we cannot publish to this zone and its live MX does not point where this preset sends mail. The panel then lists required_records with copy…
required_recordsobject[]EvetThe exact records to publish, as our preset would write them into a zone we host.

Bu uç noktanın dönderebileceği hatalar

401 · 403 · 404 · 429