POST /v1/domains/{domainId}/auth-code

Tabbatar da Asali

Aika maɓallin API azaman alamar ɗauka (bearer token). Dole ne maɓallin ya kasance yana da izinin domains.dns.manage; idan babu shi, za a ƙi amfani da maɓallin tare da lambar 403, ba 404 ba.

Wannan wurin ƙarewa ba ya buƙatar ID na ƙungiya. Maɓallin ku ya riga ya gano ƙungiyar da yake ciki, kuma an iyakance amsa a kanta.

Gwada

May gurbin komai da ke cikin kusurwa da ƙimar ka, kuma may gurbin maballi da maballi daga allon sarrafa ka.

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

An shiga? Na'urar sarrafa API da ke cikin sashin kulawarka tana cika ainihin lambar ƙungiyarka da maɓallinka naka, sannan tana gudanar da buƙatar a kan ainihin API don haka zaka iya ganin amsar gaske. Buɗe wannan tashar a cikin na'urar kula da API

Bayani

Returns the domain's EPP/auth code, which **authorizes transferring the domain to another registrar**. It is fetched from the registrar on demand, returned once, and never stored or logged by us; the response is `no-store`. A `POST` deliberately, despite reading: revealing a credential must not be something a page load, a prefetch, a browser-history entry or a cache can trigger. The reveal is audit-logged (the code itself never is). Requires `domains.dns.manage`. **422 where the registrar publishes no auth-code endpoint at all** (the Cloudflare route). The refusal names the way out rather than simply declining — a customer is entitled to leave, so support fetches the code rather than the transfer being delayed.

Sigogi

Martani

Kuskuren da wannan matsaya za ta iya maido wa

401 · 403 · 404 · 422 · 429 · 503