POST /v1/mail/services/{mailServiceId}/deliverability
Publish this domain's mail records.
प्रमाणीकरण
बेरर टोकन म्हणून API की पाठवा. की मध्ये mail.manage परवानगी असणे आवश्यक आहे; ती नसलेली की 404 ऐवजी 403 सह नाकारली जाते.
या एंडपॉइंटला कोणतीही संस्था आयडी (organisation id) लागत नाही. तुमची की (key) आधीच ती कोणत्या संस्थेशी संबंधित आहे हे ओळखते आणि प्रतिसाद त्यानुसार मर्यादित केला जातो.
प्रयत्न करा
कोनसांस्कृतिक कंसात (<>) असलेली कोणतीही गोष्ट तुमच्या स्वतःच्या मूल्यांनी बदला आणि key प्लेसहोल्डरला तुमच्या डॅशबोर्डवरील किने बदला.
curl -X POST https://api.zinndigital.com/v1/mail/services/{mailServiceId}/deliverability \
-H "Authorization: Bearer zdk_live_…" \
-H "Content-Type: application/json" \
-d '{ }'साइन इन केलेले आहे? तुमच्या डॅशबोर्डमधील API कन्सोल तुमची खरी संस्था आयडी आणि तुमची स्वतःची की आपोआप भरतो आणि लाइव्ह API विरुद्ध विनंती कार्यान्वित करतो जेणेकरून तुम्हाला वास्तविक प्रतिसाद पाहता येईल. एपी कन्सोलमध्ये हा एंडपॉइंट उघडा
तपशील
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.
पॅरामीटर्स
| नाव | प्रकार | आवश्यक | हे काय आहे |
|---|---|---|---|
mailServiceId (path) | Uuid | होय | Email service ID (UUIDv7). |
विनंती मुख्य भाग
| नाव | प्रकार | आवश्यक | हे काय आहे |
|---|---|---|---|
confirm | boolean | नाही | Required when needs_confirmation is true. Defaults to false so a destructive apply is never a side effect of clicking "fix". |
प्रतिसाद
| नाव | प्रकार | आवश्यक | हे काय आहे |
|---|---|---|---|
domain | string | होय | — |
healthy | boolean | होय | All three mechanisms present and ours - nothing to publish. |
spf_ok | boolean | होय | — |
dkim_ok | boolean | होय | — |
dmarc_ok | boolean | होय | — |
fixable | boolean | होय | 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 | होय | True when applying would replace published records, so confirm is required. |
existing_apex_mx | string[] | होय | — |
foreign_mx | string[] | होय | Apex MX targets that are not ours - the reason a fix is refused. |
foreign_spf_includes | string[] | होय | — |
would_delete | string[] | होय | 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 | होय | — |
reason | string | होय | Customer-grade English. Never a driver message. |
warnings | string[] | होय | — |
live_mx | string[] | होय | 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 | होय | False when the public MX lookup failed. A failed lookup is never read as "action needed". |
mx_ok | boolean | होय | Every live MX host is one this preset publishes, and there is at least one. |
action_needed | boolean | होय | 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[] | होय | The exact records to publish, as our preset would write them into a zone we host. |
ही एंडपॉइंट परत करू शकेल अशा त्रुटी
401 · 403 · 404 · 409 · 422 · 429