POST /v1/mail/services/{mailServiceId}/deliverability
Publish this domain's mail records.
Ìfàṣẹ́pọ̀
Fi bọ́ọ̀lù (bearer token) ranṣẹ gẹ́gẹ́ bí kọ́kọ́rọ́ API. Kọ́kọ́rọ́ náà gbọ́dọ̀ ní ìyọ̀ǹda mail.manage; a ó kọ̀ ọ́ silẹ pẹlu 403, kii ṣe 404, ti kọ́kọ́rọ́ náà kò bá ní i.
Ojú abánisọ̀rọ̀ yìí kò gba id ajọ kankan. Kọ́kọ́rọ́ rẹ ti mọ ajọ ti o jẹ ti e, a o si fèsì nipa rẹ̀.
Gbiyanju rẹ
Rọ́pọ̀ èyíkéyìí nínú àwọn àmì ìtọ́ka < > pẹ̀lú iye tirẹ̀, àti àmì ìdánimọ̀ bọ́tìnnì náà pẹ̀lú bọ́tìnnì kan láti inú dásibọ̀ọ̀dù rẹ.
curl -X POST https://api.zinndigital.com/v1/mail/services/{mailServiceId}/deliverability \
-H "Authorization: Bearer zdk_live_…" \
-H "Content-Type: application/json" \
-d '{ }'Ṣé o ti wọlé? Iwọ̀n api ní nú ìgbékalẹ̀ rẹ kún id àjọ gidi rẹ ati bọtini tirẹ, o si nṣiṣẹ ibeere na lòdì si api gidi ki o le rii esi gidi na. Ṣí ojú abáná yìí sílẹ̀ nínú kọnsólù API
Àwọn kúlẹ̀kúlẹ̀
Write the correct SPF, DKIM and DMARC records into the domain's zone. ⛔ Refuses with 422 when the apex MX is somebody else's - that is not a state to confirm past from this screen, because the customer's mail is being delivered today and this button must never be how that stops. When records would be replaced, answers 409 until confirm: true is sent, so a destructive apply is always a deliberate second act (the confirm-gated shape #622 forced on DNS). Requires mail.manage.
Àwọn ìpìlẹ̀
| Orúkọ | Iru | Tí a nílò | Kini o jẹ |
|---|---|---|---|
mailServiceId (path) | Uuid | Bẹẹni | Email service ID (UUIDv7). |
Akoonu ibeere naa
| Orúkọ | Iru | Tí a nílò | Kini o jẹ |
|---|---|---|---|
confirm | boolean | Bẹẹkọ | Required when needs_confirmation is true. Defaults to false so a destructive apply is never a side effect of clicking "fix". |
Idahun
| Orúkọ | Iru | Tí a nílò | Kini o jẹ |
|---|---|---|---|
domain | string | Bẹẹni | — |
healthy | boolean | Bẹẹni | All three mechanisms present and ours - nothing to publish. |
spf_ok | boolean | Bẹẹni | — |
dkim_ok | boolean | Bẹẹni | — |
dmarc_ok | boolean | Bẹẹni | — |
fixable | boolean | Bẹẹni | 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_confirmation | boolean | Bẹẹni | True when applying would replace published records, so confirm is required. |
existing_apex_mx | string[] | Bẹẹni | — |
foreign_mx | string[] | Bẹẹni | Apex MX targets that are not ours - the reason a fix is refused. |
foreign_spf_includes | string[] | Bẹẹni | — |
would_delete | string[] | Bẹẹni | 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_unreadable | boolean | Bẹẹni | — |
reason | string | Bẹẹni | Customer-grade English. Never a driver message. |
warnings | string[] | Bẹẹni | — |
live_mx | string[] | Bẹẹni | 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_readable | boolean | Bẹẹni | False when the public MX lookup failed. A failed lookup is never read as "action needed". |
mx_ok | boolean | Bẹẹni | Every live MX host is one this preset publishes, and there is at least one. |
action_needed | boolean | Bẹẹni | 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_records | object[] | Bẹẹni | The exact records to publish, as our preset would write them into a zone we host. |
Awọn aṣiṣe ti ibudo ipari yii le da pada
401 · 403 · 404 · 409 · 422 · 429