mail

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

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

Ҳамаи нуқтаҳои ниҳоии mail

Ҳамаи ҳуҷҷатҳои таҳиякунандагон

Санҷиши ҳаққоният

Kaliti API-ро ҳамчун рамзи доранда (bearer token) фиристед. Калит бояд дорои иҷозати mail.view бошад; калиди бидуни он бо хатои 403 рад карда мешавад, на 404.

Ин нуқтаи поёнӣ ягон рақами мушаххаси созмонро талаб намекунад. Калиди шумо аллакай созмонеро, ки ба он тааллуқ дорад, муайян мекунад ва ҷавоб ба он маҳдуд карда мешавад.

Санҷидан

Ҳар чизро дар қаavски кунҷӣ бо қиматҳои худ ва ҷойи нигоҳдорандаи калидро бо калима аз панели идоракунии худ иваз кунед.

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

Воarid шудаед? Консоли API дар панели идоракунии шумо рақами мушаххаси ташкилоти воқеӣ ва калиди худро пур мекунад ва дархостро бар зидди 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)UuidБалеEmail service ID (UUIDv7).

Ҷавоб

НомНамудТалаб карда мешавадИн чӣ аст
domainstringБале
healthybooleanБалеAll three mechanisms present and ours - nothing to publish.
spf_okbooleanБале
dkim_okbooleanБале
dmarc_okbooleanБале
fixablebooleanБалеWhether 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_confirmationbooleanБалеTrue 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 ones…
zone_unreadablebooleanБале
reasonstringБалеCustomer-grade English. Never a driver message.
warningsstring[]Бале
live_mxstring[]БалеThe 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_readablebooleanБалеFalse when the public MX lookup failed. A failed lookup is never read as "action needed".
mx_okbooleanБалеEvery live MX host is one this preset publishes, and there is at least one.
action_neededbooleanБалеThe 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[]БалеThe exact records to publish, as our preset would write them into a zone we host.

Хатоҳое, ки ин нуқтаи ниҳоӣ метавонад баргардонад

401 · 403 · 404 · 429