POST /v1/mail/services/{mailServiceId}/deliverability
Publish this domain's mail records.
Kimlik Doğrulama
Bearer token olarak bir API anahtarı gönderin. Anahtar mail.manage 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 POST https://api.zinndigital.com/v1/mail/services/{mailServiceId}/deliverability \
-H "Authorization: Bearer zdk_live_…" \
-H "Content-Type: application/json" \
-d '{ }'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
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.
Parametreler
| Ad | Tür | Zorunlu | Ne olduğu |
|---|---|---|---|
mailServiceId (path) | Uuid | Evet | Email service ID (UUIDv7). |
İstek gövdesi
| Ad | Tür | Zorunlu | Ne olduğu |
|---|---|---|---|
confirm | boolean | Hayır | Required when needs_confirmation is true. Defaults to false so a destructive apply is never a side effect of clicking "fix". |
Yanıt
| Ad | Tür | Zorunlu | Ne olduğu |
|---|---|---|---|
domain | string | Evet | — |
healthy | boolean | Evet | All three mechanisms present and ours - nothing to publish. |
spf_ok | boolean | Evet | — |
dkim_ok | boolean | Evet | — |
dmarc_ok | boolean | Evet | — |
fixable | boolean | Evet | 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 | Evet | True when applying would replace published records, so confirm is required. |
existing_apex_mx | string[] | Evet | — |
foreign_mx | string[] | Evet | Apex MX targets that are not ours - the reason a fix is refused. |
foreign_spf_includes | string[] | Evet | — |
would_delete | string[] | Evet | 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 | Evet | — |
reason | string | Evet | Customer-grade English. Never a driver message. |
warnings | string[] | Evet | — |
live_mx | string[] | Evet | 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 | Evet | False when the public MX lookup failed. A failed lookup is never read as "action needed". |
mx_ok | boolean | Evet | Every live MX host is one this preset publishes, and there is at least one. |
action_needed | boolean | Evet | 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[] | Evet | The 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 · 409 · 422 · 429