POST /v1/domains/{domainId}/registrar-guide/verify

المصادقة

أرسل مفتاح واجهة برمجة التطبيقات (API key) كرمز حامل (bearer token). يجب أن يحمل المفتاح إذن sites.view؛ والمفتاح الذي لا يملكه يُرفض بالرمز 403 وليس 404.

لا يقبل هذا الطرف أي معرف للمؤسسة. يحدد مفتاحك بالفعل المؤسسة التي ينتمي إليها، وتكون الاستجابة محصورة في نطاقها.

جربه الآن

استبدل أي شيء بين أقواس زاوية بقيمك الخاصة، والعنصر النائب للمفتاح بمفتاح من لوحة تحكمك.

curl -X POST https://api.zinndigital.com/v1/domains/{domainId}/registrar-guide/verify \
  -H "Authorization: Bearer zdk_live_…"

هل سجلت الدخول؟ تقوم وحدة تحكم واجهة برمجة التطبيقات في لوحة التحكم الخاصة بك بربط معرف مؤسستك الحقيقي ومفتاحك الخاص، وتنفذ الطلب مقابل واجهة برمجة التطبيقات المباشرة لتتمكن من رؤية الاستجابة الفعلية. افتح هذه النهاية الطرفية في وحدة تحكم 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.

المعلمات

الاستجابة

الأخطاء التي يمكن أن تُرجعها نقطة النهاية هذه

401 · 403 · 404