domains

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

Change the registrant contact (drives the registrar first).

Uthibitishaji

Tuma ufunguo wa API kama tokeni ya kubeba. Sehemu hii ya mwisho haitaji ruhusa maalum katika maelezo, kwa hivyo ipe ufunguo wako kiwango cha chini kabisa kinachohitajika na uangalie jibu badala ya kukisia.

Endpoint hii haichukui kitambulisho cha shirika. Ufunguo wako tayari unalitambua shirika linalohusika, na jibu limewekewa kikomo kwa shirika hilo pekee.

Jaribu

Badilisha chochote kilicho ndani ya mabano ya pembe na maadili yako mwenyewe, na kishikiliaji cha ufunguo na ufunguo kutoka kwa dashibodi yako.

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

Umeingia kwenye akaunti? Dashibodi yako ya kiweko cha API inajaza kitambulisho chako halisi cha shirika na ufunguo wako mwenyewe, na kuendesha ombi dhidi ya API ya moja kwa moja ili uweze kuona jibu halisi. Fungua sehemu hii ya mwisho (endpoint) kwenye konsole ya API

Maelezo

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

Vigezo

Jina	Aina	Inayohitajika	Kilicho hiki
`domainId (path)`	`Uuid`	Ndiyo	The domain's id.

Mwili wa ombi

Jina	Aina	Inayohitajika	Kilicho hiki
`first`	`string`	Ndiyo	—
`last`	`string`	Ndiyo	—
`org_name`	`string`	Hapana	—
`email`	`string`	Ndiyo	—
`phone`	`string`	Ndiyo	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[]`	Ndiyo	—
`city`	`string`	Ndiyo	—
`state`	`string`	Hapana	May be blank — most of the world has no state. The Cloudflare adapter substitutes the city where its API demands one.
`postcode`	`string`	Ndiyo	—
`country`	`string`	Ndiyo	—

Majibu

Jina	Aina	Inayohitajika	Kilicho hiki
`contact`	`DomainContact \| null`	Ndiyo	—
`editable`	`boolean`	Ndiyo	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…

Hitilafu ambazo mwisho huu unaweza kurudisha

401 · 403 · 404 · 422 · 429 · 503

PUT /v1/domains/{domainId}/contacts