GET /v1/domains/{domainId}/email-routing

Kimlik Doğrulama

Bearer token olarak bir API anahtarı gönderin. Anahtar sites.view iznine sahip olmalıdır; bu izne sahip olmayan bir anahtar 404 ile değil, 403 ile reddedilir.

Bu uç nokta hiçbir organizasyon kimliği almaz. Anahtarınız zaten ait olduğu organizasyonu tanımlar ve yanıt bu organizasyonla sınırlandırılır.

Dene

Köşeli parantez içindeki her şeyi kendi değerlerinizle ve anahtar yer tutucusunu panonuzdan bir anahtarla değiştirin.

curl -X GET https://api.zinndigital.com/v1/domains/{domainId}/email-routing \
  -H "Authorization: Bearer zdk_live_…"

Oturum açtınız mı? Panonuzdaki API konsolu, gerçek organizasyon kimliğinizi ve kendi anahtarınızı otomatik olarak doldurur ve isteği canlı API üzerinde çalıştırarak gerçek yanıtı görmenizi sağlar. Bu uç noktayı API konsolunda açın

Ayrıntılar

Cloudflare Email Routing on the customer's own account: whether it is on, the forwarding rules, the catch-all, the verified destination addresses, and the DNS the provider would publish to make it work. Scoped to the domain rather than a site, because routing is a zone-level feature — one switch and one rule set per zone however many sites hang off it. impact is the important field. Email Routing's DNS plan is apex-only: turning it on republishes the apex MX set and an apex SPF TXT, so a domain whose mail is at Google Workspace or Microsoft 365 would lose it. impact compares the provider's own published plan against the zone's live records on every read, so what the customer is warned about and what the enable endpoint refuses are the same value and cannot drift. impact.zone_unreadable is reported separately from impact.safe because "we could not read your DNS" and "your domain already receives mail elsewhere" are both unsafe and need completely different copy. addresses_readable is likewise separate from an empty addresses list: a credential may legitimately lack the account-level scope, and "we could not look" must not render as "there are none". rules_readable is the same distinction for the forwarding rules, which sit behind a different Cloudflare permission again — so a partially-scoped token returns a usable status, plan and impact with the rule list honestly marked unreadable, rather than failing the whole read. Requires sites.view. ⛔ A credential that lacks a required scope answers 422, never 503: a permission gap is the one failure a retry can never clear, and telling a customer to "try again shortly" sends them round a loop with no exit (D16780).

Parametreler

Yanıt

Bu uç noktanın dönderebileceği hatalar

401 · 403 · 404 · 422 · 429 · 503