reseller

PUT `/v1/reseller/nameservers`

Claim a domain for your own nameservers.

Autentikasi

Kirim kunci API sebagai token bearer. Kunci tersebut harus memiliki izin reseller.manage; kunci tanpa izin tersebut akan ditolak dengan status 403, bukan 404.

Tempat ID organisasi Anda dimasukkan

Titik akhir ini menerima org_id sebagai parameter kueri. Kosongkan parameter tersebut dan panggilan ini akan mencakup seluruh subpohon penyewa Anda; kirimkan untuk mempersempit panggilan ke satu organisasi.

ID organisasi Anda berada di layar kunci API di dasbor Anda, di sebelah kunci itu sendiri. Itu adalah ID yang sama dalam setiap panggilan yang Anda buat.

Coba

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

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

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

From `acme-hosting.com` we build `ns1.acme-hosting.com` and `ns2.acme-hosting.com`, served from Zinn Digital®'s own anycast DNS estate. Requires `reseller.manage` and white-label on your plan. ⛔ Claiming serves **nothing** yet. The glue records live in *your* domain, at *your* registrar, so only you can create them — publish the `A` records this returns, then call `/verify`. Until that measurement passes, your clients' zones keep the platform nameservers, because delegating a live domain to a nameserver that does not answer takes that domain off the internet. A domain Zinn® already operates is refused with `422`; a domain another reseller already holds ⇒ `409`.

Parameter

Nama	Jenis	Wajib	Tentang apa ini
`org_id (query)`	`Uuid`	Tidak	The 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…

Isi permintaan

Nama	Jenis	Wajib	Tentang apa ini
`domain`	`string`	Ya	Just the domain you own — `acme-hosting.com`, with no scheme and no `ns1.` prefix. We add `ns1` and `ns2`. A domain Zinn® operates is refused.

Tanggapan

Nama	Jenis	Wajib	Tentang apa ini
`domain`	`string`	Ya	The reseller's own domain, or `""` when they have not claimed one.
`hostnames`	`string[]`	Ya	Derived from `domain` — `ns1.acme-hosting.com`, `ns2.acme-hosting.com`. Two, because registries reject a single-nameserver delegation.
`glue`	`ResellerNameserverGlue[]`	Ya	The `A` records the reseller must register at THEIR registrar. Nothing we hold can create them: they are a registry operation on a domain we do not sponsor.
`serving`	`boolean`	Ya	—
`status`	`string`	Ya	One sentence from the last check, for the screen and for support.
`vendor`	`string`	Ya	Which of our anycast DNS providers serves these hostnames.
`checked_at`	`string`	Tidak	When it was last CHECKED, whatever the outcome. `null` means nobody has looked — a different fact from "checked and not serving".
`checked`	`boolean`	Tidak	Verify responses only. `false` means our resolver could not answer and nothing was changed — not that the glue is missing. The two send a reseller to opposite actions.
`supported_vendors`	`string[]`	Tidak	The anycast providers that can serve a nameserver brand of your own.

Kesalahan yang dapat dikembalikan oleh titik akhir ini

401 · 403 · 409 · 422 · 429