mail

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

Publish this domain's mail records.

ማረጋገጫ

የAPI ቁልፉን እንደ bearer token ይላኩ። ቁልፉ የmail.manage ፈቃድ ሊኖረው ይገባል፤ ይህ ፈቃድ የሌለው ቁልፍ በ404 ሳይሆን በ403 ውድቅ ይደረጋል።

ይህ ኤንድፖይ መክፈቻ (endpoint) የድርጅት መታወቂያ (organisation id) አይወስድም። የእርስዎ ቁልፍ (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 ኮንሶል ውስጥ ይክፈቱ

ዝርዝሮች

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

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