domains
POST /v1/domains/{domainId}/registrar-guide/verify
Check now whether this domain's nameserver change has taken effect.
身份验证
请将 API 密钥作为 bearer 令牌发送。该密钥必须具有 sites.view 权限；缺少该权限的密钥将被拒绝并返回 403 状态码，而非 404。
此端点不需要组织 ID。您的密钥已用于识别其所属的组织，且响应范围也仅限于该组织。
免费试用
将尖括号中的内容替换为您自己的值，并将键占位符替换为您仪表板中的一个键。
curl -X POST https://api.zinndigital.com/v1/domains/{domainId}/registrar-guide/verify \
-H "Authorization: Bearer zdk_live_…"已登录？您仪表板中的 API 控制台会自动填入您真实的组织 ID 和您自己的密钥，并针对实时 API 运行请求，以便您查看实际的响应。 在 API 控制台中打开此端点
详细信息
The verify button on the instruction card. Reads the live public DNS and the domain's registry record and answers in four states, so the customer can tell whether the steps they just followed worked. ⛔ Four outcomes, where GET /v1/domains/{domainId}/delegation has three, and the fourth is the point. That endpoint is a drift watch and answers delegated / not_delegated / unknown — correct for what it does. It is not sufficient here: a customer who pressed Save at their registrar thirty seconds ago is genuinely not_delegated to any resolver, because the registry has the change and nothing else does yet. Telling them "not yet" is true, useless, and reads as failure. propagating is that state told honestly — the registry has the pair we asked for and public DNS has not caught up — and it is a success message, not a warning. ⛔ unknown is not not_delegated. They send a customer to opposite actions, and a lookup that failed must never be rendered as "you have not done it". expected is resolved per domain from the zone's own nameservers where the DNS provider assigns them, so a footprint-free domain is compared against its own pair rather than a platform constant. observed is what it points at right now — public DNS where that answered, the registry's record otherwise. Writes nothing. The recorded reading, the drift ladder and the "your domain has left us" alarm belong to GET/POST /v1/domains/{domainId}/delegation; a customer pressing a button on an instruction card is asking a question, not supplying evidence. POST rather than GET only because it makes two live outbound lookups and must never be cached or prefetched. Requires sites.view, RLS-scoped. It changes nothing about the domain, and gating it behind a management permission would leave a read-only user looking at instructions they can never confirm they have followed.
参数
| 名称 | 类型 | 必填 | 内容简介 |
|---|---|---|---|
domainId (path) | Uuid | 是 | The domain's id. |
响应
| 名称 | 类型 | 必填 | 内容简介 |
|---|---|---|---|
outcome | string<delegated, propagating, not_delegated, unknown> | 是 | delegated = done. propagating = the registry has our pair and public DNS has not caught up; the customer did it right and must simply wait. not_delegated = a real reading… |
expected | string[] | 是 | The pair to set, resolved per domain from the zone's own nameservers where the provider assigns them — never a platform constant (D1034). |
observed | string[] | 是 | Where it points right now — public DNS where that answered, the registry's record otherwise. Empty means the reading was positive and there was nothing there, not that the reading… |
recheck_after_seconds | integer | 是 | Roughly how long to wait before pressing again, or null when there is nothing to wait for. A hint about the interface, not a claim about DNS propagation. |
此端点可能返回的错误
401 · 403 · 404