API ReferenceDomainDomain LifecycleDomains & DNSv1 (Legacy)Manage Domain SettingsUpdate domain PATCH
Update domain
View as MarkdownUpdates domain settings.
Full description
Updates domain settings. Only fields included in the request body are modified. Returns 204 No Content.
Authorization
bearerAuth AuthorizationBearer <token>
Personal Access Token (PAT). Generate one from the developer dashboard. Pass as: Authorization: Bearer .
In: header
Path Parameters
domain*string
Domain whose Contacts are to be updated.
Header Parameters
X-Shopper-Id?string
Shopper ID which owns the domain. NOTE: This is only required if you are a Reseller managing a domain purchased outside the scope of your reseller account.
Changes to apply to existing Contacts
Response Body
curl -X PATCH "https://example.com/v1/domains/string/contacts" \ -H "Content-Type: application/json" \ -d '{ "contactRegistrant": { "addressMailing": { "address1": "string", "city": "string", "country": "AC", "postalCode": "string", "state": "string" }, "email": "user@example.com", "nameFirst": "string", "nameLast": "string", "phone": "string" } }'Empty
Agent & Automation Notes
Scopes
domains.domain:read, domains.domain:create, domains.domain:delete, domains.domain:update, domains.contact:update, domains.dns:update, domains.transfer:executeRate limit60 req/min per credential
On failureGET operations are safe to retry. PUT/PATCH DNS are idempotent by shape. POST purchase is NOT idempotent — verify state before retrying.
Related
Last updated on
How is this guide?