mail

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

Publish this domain's mail records.

Dhammaan mail bixiyayaasha

Xaqiijinta aqoonsiga

U dir furaha API ah calaamad dusha ah (bearer token). Furaha waa inuu wataa ruqadda mail.manage; furaha aan wadan waxaa loo diidayaa 403, ee ma aha 404.

Boggan ma qaato aqoonsiga ururka. Furahaagu wuxuu horay u aqoonsanayaa ururka uu ka tirsan yahay, jawaabtuna waxay ku kooban tahay halkaas.

Isku day

Ku beddel wax kasta oo ku dhex jira qeebaha xaglaha ah qiimayaashaada, sidoo kalena haystaaha furaha ku beddel fure ka dhex muuqda dashboordigaaga.

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

Ma sign-garaysay? Qalabka API ee ku jira dashboard-kaagu wuxuu buuxiyaa aqoonsigaaga ururka ee dhabta ah iyo furahaaga gaarka ah, wuxuuna ku shaqeysiiyaa codsiga API-ga nool si aad u aragto jawaabta dhabta ah. Kani ka fur barta kontoroolka ee API

Details

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`.

Cabiraha

MagacaNoocLoo baahan yahayMaxay tahay
mailServiceId (path)UuidHaaEmail service ID (UUIDv7).

Codsiga jidhkiisa

MagacaNoocLoo baahan yahayMaxay tahay
confirmbooleanMayaRequired when `needs_confirmation` is true. Defaults to false so a destructive apply is never a side effect of clicking "fix".

Jawaab

MagacaNoocLoo baahan yahayMaxay tahay
domainstringHaa
healthybooleanHaaAll three mechanisms present and ours - nothing to publish.
spf_okbooleanHaa
dkim_okbooleanHaa
dmarc_okbooleanHaa
fixablebooleanHaaWhether 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_confirmationbooleanHaaTrue when applying would replace published records, so `confirm` is required.
existing_apex_mxstring[]Haa
foreign_mxstring[]HaaApex MX targets that are not ours - the reason a fix is refused.
foreign_spf_includesstring[]Haa
would_deletestring[]HaaRecords 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 one…
zone_unreadablebooleanHaa
reasonstringHaaCustomer-grade English. Never a driver message.
warningsstring[]Haa

Cilladaha ay bartaani soo celin karto

401 · 403 · 404 · 409 · 422 · 429