reseller

POST /v1/reseller/brand/sending-domain

Send your clients' e-mail from your own domain.

所有 reseller 端点

身份验证

请将 API 密钥作为 bearer 令牌发送。该密钥必须具有 reseller.manage 权限;缺少该权限的密钥将被拒绝并返回 403 状态码,而非 404。

您的组织 ID 应填在此处

此端点将 org_id 作为查询参数。不填则调用涵盖您的整个租户子树;发送该参数则将调用范围缩小到一个组织。

您的组织ID位于控制面板的API密钥屏幕上,就在密钥本身的旁边。这是您在每次调用时使用的相同ID。

免费试用

将尖括号中的内容替换为您自己的值,并将键占位符替换为您仪表板中的一个键。

curl -X POST https://api.zinndigital.com/v1/reseller/brand/sending-domain \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "domain": <string> }'

已登录?您仪表板中的 API 控制台会自动填入您真实的组织 ID 和您自己的密钥,并针对实时 API 运行请求,以便您查看实际的响应。 在 API 控制台中打开此端点

详细信息

Registers a sending domain and returns the DNS records to publish. Requires `reseller.manage`. ⛔ **This is the largest single white-label leak and no template change could close it.** Everything inside a notification was already resolved to your brand — the name, the call-to-action link — while the envelope still read `Zinn Digital® Billing <billing@zinndigital.com>`, which is the line your client actually looks at. ⛔ Attaching does **not** switch the sender. Publish the records, then call `/verify`; only a successful verification moves your mail onto your domain, because mail from an unverified domain does not arrive. A domain is already attached ⇒ `409`. Remove it first — replacing it silently would orphan the previous one at the provider.

参数

名称类型必填内容简介
org_id (query)UuidThe organization this call acts on. Optional for a caller with exactly one direct membership; **required** for anyone with more than one — which is every reseller and every agen…

请求正文

名称类型必填内容简介
domainstringJust the domain — `acme.com` or `mail.acme.com`, with no scheme and no path.

响应

名称类型必填内容简介
domainstring
verifiedbooleanThe mail provider's answer. Never inferred from `domain` being set.
providerstring
provider_statusstringThe provider's raw status word, for display. Never branch on it.
recordsBrandDnsRecord[]

此端点可能返回的错误

401 · 403 · 409 · 422 · 429 · 503