mail

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

Publish this domain's mail records.

सबै mail इन्डपइन्टहरू

सबै विकासकर्ता कागजातहरू

प्रमाणीकरण

एपिआई कुञ्जीलाई बियरर टोकन (bearer token) को रूपमा पठाउनुहोस्। कुञ्जीसँग mail.manage अनुमति हुनुपर्छ; अनुमति नभएको कुञ्जीलाई 404 होइन, 403 मार्फत अस्वीकार गरिन्छ।

यो इन्डपोइन्टले कुनै संस्थाको आइडी लिँदैन। तपाईंको कुञ्जीले यस अन्तर्गत पर्ने संस्थालाई पहिल्यै पहिचान गर्छ, र प्रतिक्रिया त्यसैमा सीमित हुन्छ।

प्रयास गर्नुहोस्

कोणीय कोष्ठकभित्र भएका जुनसुकै कुरालाई आफ्नो मानहरूद्वारा बदल्नुहोस्, र मुख्य स्थानहोल्डरलाई तपाईंको ड्यासबोर्डको कुञ्जीद्वारा बदल्नुहोस्।

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 विरुद्ध अनुरोध चलाउँछ ताकि तपाईंले वास्तविक प्रतिक्रिया हेर्न सक्नुहोस्। यो एन्डपोइन्टलाई 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).

अनुरोध बडी

नामप्रकारआवश्यकयो के हो
confirmbooleanहैनRequired when needs_confirmation is true. Defaults to false so a destructive apply is never a side effect of clicking "fix".

प्रतिक्रिया

नामप्रकारआवश्यकयो के हो
domainstringहुन्छ
healthybooleanहुन्छAll three mechanisms present and ours - nothing to publish.
spf_okbooleanहुन्छ
dkim_okbooleanहुन्छ
dmarc_okbooleanहुन्छ
fixablebooleanहुन्छ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_confirmationbooleanहुन्छTrue when applying would replace published records, so confirm is required.
existing_apex_mxstring[]हुन्छ
foreign_mxstring[]हुन्छApex MX targets that are not ours - the reason a fix is refused.
foreign_spf_includesstring[]हुन्छ
would_deletestring[]हुन्छ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_unreadablebooleanहुन्छ
reasonstringहुन्छCustomer-grade English. Never a driver message.
warningsstring[]हुन्छ
live_mxstring[]हुन्छ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_readablebooleanहुन्छFalse when the public MX lookup failed. A failed lookup is never read as "action needed".
mx_okbooleanहुन्छEvery live MX host is one this preset publishes, and there is at least one.
action_neededbooleanहुन्छ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_recordsobject[]हुन्छThe exact records to publish, as our preset would write them into a zone we host.

यो इन्डपोइन्टले फर्काउन सक्ने त्रुटिहरू

401 · 403 · 404 · 409 · 422 · 429