mail

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

Publish this domain's mail records.

Dukkan mail wuraren ƙarshe

Dukan takardun mai haɓakawa

Tabbatar da Asali

Aika maɓallin API azaman alamar ɗauka (bearer token). Dole ne maɓallin ya kasance yana da izinin mail.manage; idan babu shi, za a ƙi amfani da maɓallin tare da lambar 403, ba 404 ba.

Wannan wurin ƙarewa ba ya buƙatar ID na ƙungiya. Maɓallin ku ya riga ya gano ƙungiyar da yake ciki, kuma an iyakance amsa a kanta.

Gwada

May gurbin komai da ke cikin kusurwa da ƙimar ka, kuma may gurbin maballi da maballi daga allon sarrafa ka.

curl -X POST https://api.zinndigital.com/v1/mail/services/{mailServiceId}/deliverability \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{  }'

An shiga? Na'urar sarrafa API da ke cikin sashin kulawarka tana cika ainihin lambar ƙungiyarka da maɓallinka naka, sannan tana gudanar da buƙatar a kan ainihin API don haka zaka iya ganin amsar gaske. Buɗe wannan tashar a cikin na'urar kula da API

Bayani

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.

Sigogi

SunaNau'iAna buƙataAbin da yake
mailServiceId (path)UuidEhEmail service ID (UUIDv7).

Jikin buƙata

SunaNau'iAna buƙataAbin da yake
confirmbooleanA'aRequired when needs_confirmation is true. Defaults to false so a destructive apply is never a side effect of clicking "fix".

Martani

SunaNau'iAna buƙataAbin da yake
domainstringEh
healthybooleanEhAll three mechanisms present and ours - nothing to publish.
spf_okbooleanEh
dkim_okbooleanEh
dmarc_okbooleanEh
fixablebooleanEhWhether 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_confirmationbooleanEhTrue when applying would replace published records, so confirm is required.
existing_apex_mxstring[]Eh
foreign_mxstring[]EhApex MX targets that are not ours - the reason a fix is refused.
foreign_spf_includesstring[]Eh
would_deletestring[]EhRecords 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_unreadablebooleanEh
reasonstringEhCustomer-grade English. Never a driver message.
warningsstring[]Eh
live_mxstring[]EhThe 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_readablebooleanEhFalse when the public MX lookup failed. A failed lookup is never read as "action needed".
mx_okbooleanEhEvery live MX host is one this preset publishes, and there is at least one.
action_neededbooleanEhThe 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[]EhThe exact records to publish, as our preset would write them into a zone we host.

Kuskuren da wannan matsaya za ta iya maido wa

401 · 403 · 404 · 409 · 422 · 429