GET /v1/mail/routing

Ìfàṣẹ́pọ̀

Fi bọ́ọ̀lù (bearer token) ranṣẹ gẹ́gẹ́ bí kọ́kọ́rọ́ API. Kọ́kọ́rọ́ náà gbọ́dọ̀ ní ìyọ̀ǹda mail.view; a ó kọ̀ ọ́ silẹ pẹlu 403, kii ṣe 404, ti kọ́kọ́rọ́ náà kò bá ní i.

Ojú abánisọ̀rọ̀ yìí kò gba id ajọ kankan. Kọ́kọ́rọ́ rẹ ti mọ ajọ ti o jẹ ti e, a o si fèsì nipa rẹ̀.

Gbiyanju rẹ

Rọ́pọ̀ èyíkéyìí nínú àwọn àmì ìtọ́ka < > pẹ̀lú iye tirẹ̀, àti àmì ìdánimọ̀ bọ́tìnnì náà pẹ̀lú bọ́tìnnì kan láti inú dásibọ̀ọ̀dù rẹ.

curl -X GET https://api.zinndigital.com/v1/mail/routing \
  -H "Authorization: Bearer zdk_live_…"

Ṣé o ti wọlé? Iwọ̀n api ní nú ìgbékalẹ̀ rẹ kún id àjọ gidi rẹ ati bọtini tirẹ, o si nṣiṣẹ ibeere na lòdì si api gidi ki o le rii esi gidi na. Ṣí ojú abáná yìí sílẹ̀ nínú kọnsólù API

Àwọn kúlẹ̀kúlẹ̀

One row per domain: which mechanism serves its mail, where its catch-all delivers, and whether the world agrees yet. Requires mail.view. ⛔ A different question from /v1/mail/services, and the reason this endpoint had to exist. A forwarding domain — the whole Footprint-Free line — deliberately has no mail service: it gets an alias that receives rather than a mailbox that stores, so it appears in no service list at any depth. Before this route, that customer could not see that their site forwards, could not see where to, and could not change it. mechanism is derived, never chosen: it is a function of the customer's own mail connection, the plan's mailbox allowance, and the domain's live DNS delegation — and a zone on Cloudflare is routed through Cloudflare Email Routing automatically, because it is free there and keeps the traffic off our relay. mechanism_label is the sentence explaining that choice, and it is the same one the operator log carries.

Idahun

Awọn aṣiṣe ti ibudo ipari yii le da pada

401 · 403 · 429