mail

GET /v1/mail/preflight

What setting email up on a domain would do to its DNS.

Wszystkie punkty końcowe mail

Uwierzytelnianie

Wyślij klucz API jako token bearer. Klucz musi posiadać uprawnienie mail.view; klucz bez niego jest odrzucany z kodem 403, a nie 404.

Miejsce na identyfikator organizacji

Ten punkt końcowy przyjmuje org_id jako parametr zapytania. Pomiń go, a wywołanie obejmie całe drzewo dzierżawy; prześlij go, aby ograniczyć wywołanie do jednej organizacji.

Identyfikator Twojej organizacji znajduje się na ekranie kluczy API w Twoim panelu, obok samego klucza. Jest to ten sam identyfikator w każdym wywołaniu, które wykonujesz.

Wypróbuj

Zastąp wszystko w nawiasach ostrych własnymi wartościami, a zastępczy znacznik klucza kluczem ze swojego pulpitu nawigacyjnego.

curl -X GET https://api.zinndigital.com/v1/mail/preflight?fqdn=<fqdn> \
  -H "Authorization: Bearer zdk_live_…"

Zalogowany? Konsola API w Twoim panelu uzupełnia rzeczywiste identyfikator organizacji oraz Twój własny klucz i wykonuje żądanie względem aktywnego API, dzięki czemu możesz zobaczyć rzeczywistą odpowiedź. Otwórz ten punkt końcowy w konsoli API

Szczegóły

Read-only. Answers **before the customer commits** whether this domain can take our mail records, and exactly what publishing them would remove (#662). Setting mail up rewrites the domain's apex `MX`. If the domain already receives email somewhere else, that stops inbound mail reaching the mailboxes it is addressed to — an outage the customer usually learns about from the people who could not reach them. Without this endpoint the only way to discover the refusal was to create a service and watch it fail asynchronously, which is a refusal arriving *after* the decision. `safe: false` means `POST /v1/mail/services` will refuse unless it is called with the override flag. `foreign_mx` and `would_delete` are listed **verbatim**, not counted, because a customer must be able to see what they are about to destroy before confirming it. `zone_unreadable: true` is **never** `safe`: there is no DNS resolver in the platform, so "we could not read the zone" is the normal answer for a domain whose DNS is hosted elsewhere, and treating that as safe would disable the guard exactly where it matters most. ⚠️ A safe answer is not a promise — the zone can change between this call and the apply, so provisioning repeats the check inside its workflow. Requires `mail.view`.

Parametry

NazwaTypWymaganeCo to jest
fqdn (query)stringTakThe domain to check.
provider (query)MailProviderNieWhich provider's records to test against; defaults to our own mail. The answer differs per provider, because each preset publishes a different record set.
mx_hosts (query)stringNie`custom` only: the MX targets the reseller has typed so far, comma-separated. The preflight compares the zone with the records the preset **would** publish, and for a provider w…
org_id (query)UuidNieThe organization to act in; defaults to the caller's own when unambiguous.

Odpowiedź

NazwaTypWymaganeCo to jest
domainstringTakThe domain that was checked, normalised.
safebooleanTakWhether an apply would proceed without the override flag. `false` means `POST /v1/mail/services` returns 409 unless the customer confirms.
existing_apex_mxstring[]TakEvery apex `MX` currently published, in the order DNS returned them.
foreign_mxstring[]TakThe apex `MX` targets that are not ours to replace — the reason for a refusal, and the list the customer must see before confirming an override.
foreign_spf_includesstring[]Tak`include:` mechanisms in the current SPF that the new record would drop.
would_deletestring[]TakRecords the apply would remove or replace, as `"NAME TYPE VALUE"`.
zone_unreadablebooleanTakThe zone could not be read at all — never `safe`. Distinct from "read it, found nothing", because the two need different copy: one is "we cannot see your DNS", the other is "you…
reasonstringTakCustomer-grade English describing what was found. Empty when safe.
warningsstring[]TakNon-blocking observations about the zone.

Błędy, które ten punkt końcowy może zwrócić

401 · 403 · 422 · 429 · 503