domains

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

Change the registrant contact (drives the registrar first).

Pagpapatotoo

Magpadala ng API key bilang bearer token. Ang endpoint na ito ay hindi naglatag ng tiyak na pahintulot sa pagtutukoy, kaya ibigay sa iyong key ang pinakamababang kailangan nito at suriin ang tugon sa halip na umasa.

Ang endpoint na ito ay hindi nangangailangan ng id ng organisasyon. Natutukoy na ng iyong key ang organisasyong kinabibilangan nito, at nakatuon ang tugon dito.

Subukan ito

Palitan ang anuman sa loob ng mga panaklong na may anggulo ng iyong sariling mga halaga, at ang placeholder ng key na may key mula sa iyong dashboard.

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

Nakalagda? Ang API console sa iyong dashboard ay awtomatikong naglalagay ng iyong tunay na ID ng organisasyon at sariling susi, at pinapatakbo ang kahilingan laban sa live na API upang makita mo ang aktwal na tugon. Buksan ang endpoint na ito sa console ng API

Mga Detalye

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

Mga Parameter

Pangalan	Uri	Kailangan	Ano ito
`domainId (path)`	`Uuid`	Oo	The domain's id.

Katawan ng kahilingan

Pangalan	Uri	Kailangan	Ano ito
`first`	`string`	Oo	—
`last`	`string`	Oo	—
`org_name`	`string`	Hindi	—
`email`	`string`	Oo	—
`phone`	`string`	Oo	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[]`	Oo	—
`city`	`string`	Oo	—
`state`	`string`	Hindi	May be blank — most of the world has no state. The Cloudflare adapter substitutes the city where its API demands one.
`postcode`	`string`	Oo	—
`country`	`string`	Oo	—

Tugon

Pangalan	Uri	Kailangan	Ano ito
`contact`	`DomainContact \| null`	Oo	—
`editable`	`boolean`	Oo	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…

Mga error na maibabalik ng endpoint na ito

401 · 403 · 404 · 422 · 429 · 503

PUT /v1/domains/{domainId}/contacts