domains

PUT `/v1/domains/{domainId}/contacts`

Change the registrant contact (drives the registrar first).

Pengesahan

Hantar kunci API sebagai token pembawa. Titik akhir ini tidak menyatakan kebenaran tertentu dalam spesifikasi, jadi berikan kunci anda kebenaran minimum yang diperlukan dan semak respons tersebut daripada membuat andaian.

Titik akhir ini tidak memerlukan id organisasi. Kunci anda telah mengenal pasti organisasi kepunyaannya, dan respons dis skopkan kepadanya.

Cuba

Gantikan apa sahaja di dalam kurungan sudut dengan nilai anda sendiri, dan pemegang tempat kunci dengan kunci dari papan pemuka anda.

curl -X PUT https://api.zinndigital.com/v1/domains/{domainId}/contacts \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "first": <string>, "last": <string>, "email": <string>, "phone": <string>, "street": <string[]>, "city": <string>, "postcode": <string>, "country": <string> }'

Sudah log masuk? Konsol API dalam papan pemuka anda mengisi id organisasi sebenar dan kunci anda sendiri, serta menjalankan permintaan terhadap API langsung supaya anda boleh melihat respons sebenar. Buka penamat ini dalam konsol API

Butiran

**This is not a preference.** The registrant address is the ICANN record of who owns the domain and is what the registry emails to verify the registration — an unverified or bouncing one gets the domain **suspended**, so a customer who moves house or changes email needs to be able to correct it. The registrar is driven **first** and our mirror is written only once it accepted. The reverse order would show a customer their new address over a registry that still holds the old one. **Every field is required.** ICANN treats a registrant change as one record, several registries re-verify the whole contact on any change, and the drivers replace the set rather than patching a field — so a partial body would merge into whatever our mirror happened to hold. `422` where the registrar cannot change contacts at all (the Cloudflare route), naming support rather than telling the customer to retry something that will never work. `503` where it could not, which is worth retrying.

Parameter

Nama	Jenis	Diperlukan	Apakah ia
`domainId (path)`	`Uuid`	Ya	The domain's id.

Badan permintaan

Nama	Jenis	Diperlukan	Apakah ia
`first`	`string`	Ya	—
`last`	`string`	Ya	—
`org_name`	`string`	Tidak	—
`email`	`string`	Ya	—
`phone`	`string`	Ya	E.164-ish. Validated permissively on purpose — the registry is the authority on what it accepts, and a client-side rule that refused a legitimate international number would be a…
`street`	`string[]`	Ya	—
`city`	`string`	Ya	—
`state`	`string`	Tidak	May be blank — most of the world has no state. The Cloudflare adapter substitutes the city where its API demands one.
`postcode`	`string`	Ya	—
`country`	`string`	Ya	—

Respons

Nama	Jenis	Diperlukan	Apakah ia
`contact`	`DomainContact \| null`	Ya	—
`editable`	`boolean`	Ya	Whether this domain's registrar publishes a contact-update path. `false` on the Cloudflare route; the console renders the panel read-only rather than offering a control that ans…

Ralat yang boleh dikembalikan oleh titik akhir ini

401 · 403 · 404 · 422 · 429 · 503

PUT /v1/domains/{domainId}/contacts