GET /v1/domains/routes

Autentikasi

Kirimkan kunci API sebagai token bearer. Titik akhir ini tidak menyatakan izin tertentu dalam spesifikasi, jadi berikan kunci Anda izin minimum yang diperlukan dan periksa responsnya alih-alih berasumsi.

Coba

Ganti apa pun di dalam tanda kurung sudut dengan nilai Anda sendiri, dan placeholder kunci dengan kunci dari dasbor Anda.

curl -X GET https://api.zinndigital.com/v1/domains/routes \
  -H "Authorization: Bearer zdk_live_…"

Sudah masuk? Konsol API di dasbor Anda akan mengisi ID organisasi asli dan kunci Anda sendiri, serta menjalankan permintaan terhadap API langsung sehingga Anda dapat melihat respons aktualnya. Buka titik akhir ini di konsol API

Detail

Cloudflare Registrar is offered as **an additional, deliberately-chosen way to register a domain**, beside the organisation's existing registrar — not as a cheaper source the platform switches to silently. The reason the choice is the customer's is `locks_nameservers`. A Cloudflare registration cannot use external nameservers: the API exposes no way to set them, so the domain's DNS stays with Cloudflare for as long as we hold it. That is a constraint somebody has to accept knowingly, not one to discover the first time they try to point the domain elsewhere. Every flag is derived from the registrar driver's advertised capabilities, so a driver that gains or loses an endpoint moves this copy with it. Routes the organisation cannot use are returned with `available: false` and a reason rather than filtered out — a one-option list is indistinguishable from a list whose second option failed to load.

Parameter

Tanggapan

Kesalahan yang dapat dikembalikan oleh titik akhir ini

401 · 403 · 422 · 429