POST /v1/mail/services/{mailServiceId}/deliverability
Publish this domain's mail records.
Autentifikacija
Pošaljite API ključ kao nosivi token. Ključ mora imati dozvolu mail.manage; ključ bez nje se odbija s kodom 403, a ne 404.
Ova krajnja točka ne prihvaća ID organizacije. Vaš ključ već identificira organizaciju kojoj pripada, a odgovor je ograničen na nju.
Isprobajte
Zamijenite sve unutar šiljastih zagrada svojim vlastitim vrijednostima, a rezervirano mjesto za ključ s ključem iz vaše nadzorne ploče.
curl -X POST https://api.zinndigital.com/v1/mail/services/{mailServiceId}/deliverability \
-H "Authorization: Bearer zdk_live_…" \
-H "Content-Type: application/json" \
-d '{ }'Prijavljeni ste? API konzola na vašoj nadzornoj ploči automatski unosi stvarni ID vaše organizacije i vaš vlastiti ključ te šalje zahtjev prema aktivnom API-ju kako biste mogli vidjeti stvarni odgovor. Otvori ovu krajnju točku u API konzoli
Pojedinosti
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.
Parametri
| Naziv | Vrsta | Obavezno | Što je to |
|---|---|---|---|
mailServiceId (path) | Uuid | Da | Email service ID (UUIDv7). |
Tijelo zahtjeva
| Naziv | Vrsta | Obavezno | Što je to |
|---|---|---|---|
confirm | boolean | Ne | Required when needs_confirmation is true. Defaults to false so a destructive apply is never a side effect of clicking "fix". |
Odgovor
| Naziv | Vrsta | Obavezno | Što je to |
|---|---|---|---|
domain | string | Da | — |
healthy | boolean | Da | All three mechanisms present and ours - nothing to publish. |
spf_ok | boolean | Da | — |
dkim_ok | boolean | Da | — |
dmarc_ok | boolean | Da | — |
fixable | boolean | Da | 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 | Da | True when applying would replace published records, so confirm is required. |
existing_apex_mx | string[] | Da | — |
foreign_mx | string[] | Da | Apex MX targets that are not ours - the reason a fix is refused. |
foreign_spf_includes | string[] | Da | — |
would_delete | string[] | Da | 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 | Da | — |
reason | string | Da | Customer-grade English. Never a driver message. |
warnings | string[] | Da | — |
live_mx | string[] | Da | 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 | Da | False when the public MX lookup failed. A failed lookup is never read as "action needed". |
mx_ok | boolean | Da | Every live MX host is one this preset publishes, and there is at least one. |
action_needed | boolean | Da | 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[] | Da | The exact records to publish, as our preset would write them into a zone we host. |
Pogreške koje ova krajnja točka može vratiti
401 · 403 · 404 · 409 · 422 · 429