domains

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

Change the registrant contact (drives the registrar first).

Xaqiijinta aqoonsiga

U dir fure API ahaan calaamad muujisa (bearer token). Barta dhammaadka ee kani ma caysino luqad ahaan oggolaansho gaar ah oo ku dhex jirta qeexidda, markaa sii furahaaga inta ugu yar ee uu u baahan yahay oo fiiri jawaabta halka aad wax ka qaadan lahayd.

Boggan ma qaato aqoonsiga ururka. Furahaagu wuxuu horay u aqoonsanayaa ururka uu ka tirsan yahay, jawaabtuna waxay ku kooban tahay halkaas.

Isku day

Ku beddel wax kasta oo ku dhex jira qeebaha xaglaha ah qiimayaashaada, sidoo kalena haystaaha furaha ku beddel fure ka dhex muuqda dashboordigaaga.

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> }'

Ma sign-garaysay? Qalabka API ee ku jira dashboard-kaagu wuxuu buuxiyaa aqoonsigaaga ururka ee dhabta ah iyo furahaaga gaarka ah, wuxuuna ku shaqeysiiyaa codsiga API-ga nool si aad u aragto jawaabta dhabta ah. Kani ka fur barta kontoroolka ee API

Faahfaahin

**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.

Cabiraha

Magaca	Nooc	Loo baahan yahay	Maxay tahay
`domainId (path)`	`Uuid`	Haa	The domain's id.

Codsiga jidhkiisa

Magaca	Nooc	Loo baahan yahay	Maxay tahay
`first`	`string`	Haa	—
`last`	`string`	Haa	—
`org_name`	`string`	Maya	—
`email`	`string`	Haa	—
`phone`	`string`	Haa	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[]`	Haa	—
`city`	`string`	Haa	—
`state`	`string`	Maya	May be blank — most of the world has no state. The Cloudflare adapter substitutes the city where its API demands one.
`postcode`	`string`	Haa	—
`country`	`string`	Haa	—

Jawaab

Magaca	Nooc	Loo baahan yahay	Maxay tahay
`contact`	`DomainContact \| null`	Haa	—
`editable`	`boolean`	Haa	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…

Cilladaha ay bartaani soo celin karto

401 · 403 · 404 · 422 · 429 · 503

PUT /v1/domains/{domainId}/contacts