Change the registrant of a bought domain
update_domain_registrant
Replaces the registrant of a domain the workspace bought, the person or company that legally owns it.
Every required field of contact has to be sent, so the tool tells the client to read the current Contact with get_bought_domain and change only what you asked for. Phone has to be a possible number for its country code and is saved in E.164 form, such as +14155550100, and Country takes XK for Kosovo, as on buy_domain. A change of owner can lock transfers for 60 days, and a new email, name or company can make Name.com email the registrant a link to confirm their email again, which Verification on get_bought_domain tracks.
The answer is the domain as get_bought_domain reads it. Only the workspace owner can do this, and the domain must be active or expiring. The workspace can make 30 domain changes a minute, shared with the Domains page and covering DNS records, nameservers, the registrant, the transfer lock, auto-renew and transfer codes, and a refusal says how long to wait. See Change the registrant.
Request
Call it with a POST to https://api.modulify.ai/v1/update_domain_registrant, sending the inputs below as a JSON object. The token needs the domains:write scope.
This method is marked destructive: it deletes or overwrites data. Check the inputs before you call it, and send an Idempotency-Key header whenever you might retry it.
curl -X POST https://api.modulify.ai/v1/update_domain_registrant \
-H "Authorization: Bearer YOUR_TOKEN" \
-H "Content-Type: application/json" \
-d '{"workspaceId":"WORKSPACE_ID","domainId":"DOMAIN_ID","contact":{}}'Over MCP, the same method is the update_domain_registrant tool.
Inputs
| Input | Type | Required | Description |
|---|---|---|---|
workspaceId |
string | Yes | The workspace that owns the domain. |
domainId |
string | Yes | The _id of the bought domain, from list_bought_domains. |
contact |
object | Yes | The registrant as it should be afterwards, with the fields buy_domain takes. FirstName, LastName, Email, Phone, Address1, City, State, Zip and Country are required, and CompanyName and Address2 are optional. |
Response
Every call answers with the JSON envelope of success, message, data, code and version. data holds the result described above, and on a method that returns a total, count carries it. The response headers carry the call's X-Request-Id and what is left of your per-minute budget in X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset. Errors explains every status code a call can answer with.