Search in this section
Description
The contact update command updates an existing contact. If the contact is used at different registries, the respective updates are carried out asynchronously and a system message is provided when polling.
XML example
<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> <command> <update> <contact:update xmlns:contact="urn:ietf:params:xml:ns:contact-1.0"> <contact:id>11268444</contact:id> <contact:chg> <contact:postalInfo type="loc"> <contact:addr> <contact:street>124 Example Dr.</contact:street> <contact:street>Suite 200</contact:street> <contact:city>Dulles</contact:city> <contact:sp>VA</contact:sp> <contact:pc>20166-6503</contact:pc> <contact:cc>US</contact:cc> </contact:addr> </contact:postalInfo> <contact:email>jon.doe@domain.com</contact:email> <contact:voice>+1.7034444444</contact:voice> </contact:chg> </contact:update> </update> <clTRID>ABC-12345</clTRID> </command> </epp>
<epp xmlns:domain="urn:ietf:params:xml:ns:domain-1.0" xmlns:domainrobot="urn:org:domainrobot:ns:ext-1.0" xmlns:contact="urn:ietf:params:xml:ns:contact-1.0" xmlns:pro="urn:org:domainrobot:ns:contact:pro-1.0" xmlns:ro="urn:org:domainrobot:ns:contact:ro-1.0" xmlns:xxx="urn:org:domainrobot:ns:contact:xxx-1.0" xmlns:ca="urn:org:domainrobot:ns:contact:ca-1.0" xmlns:cat="urn:org:domainrobot:ns:contact:cat-1.0" xmlns="urn:ietf:params:xml:ns:epp-1.0" xmlns:jobs="urn:org:domainrobot:ns:contact:jobs-1.0" xmlns:rgp="urn:ietf:params:xml:ns:rgp-1.0" xmlns:aero="urn:org:domainrobot:ns:contact:aero-1.0" xmlns:host="urn:ietf:params:xml:ns:host-1.0" xmlns:hk="urn:org:domainrobot:ns:contact:hk-1.0" xmlns:bank="urn:org:domainrobot:ns:contact:bank-1.0" xmlns:it="urn:org:domainrobot:ns:contact:it-1.0" xmlns:barcelona="urn:org:domainrobot:ns:contact:barcelona-1.0" xmlns:au="urn:org:domainrobot:ns:contact:au-1.0" xmlns:uk="urn:org:domainrobot:ns:contact:uk-1.0" xmlns:swiss="urn:org:domainrobot:ns:contact:swiss-1.0" xmlns:ru="urn:org:domainrobot:ns:contact:ru-1.0"> <response> <result code="1000"> <msg lang="en">Command completed successfully</msg> </result> <trID> <clTRID>ABC-12345</clTRID> <svTRID>DEF-12345</svTRID> </trID> </response> </epp>
Note
- The values name and org can not be updated.
- The contact extension type can not be updated.
- EPP add/rem of Status is not supported and will return an error.
Updating the TLD / contact extensions
The existing TLD / contact extensions are always transmitted and merged when they are updated. Below are several examples which cover certain operations.
Updating the TLD / Contact extensions
The extension website of the TLD .jobs is to be updated. The original value was "myhomepage.com" and is to be updated to "mynewhomepage.com". It is important to always send the complete block when updating.
Update .jobs extension
<jobs:contact xmlns:jobs="urn:org:domainrobot:ns:contact:jobs-1.0"> <jobs:adminType>0</jobs:adminType> <jobs:contactTitle>Herr</jobs:contactTitle> <jobs:hrMember>0</jobs:hrMember> <jobs:website>mynewhomepage.com</jobs:website> </jobs:contact>
The extension website of the TLD .jobs is to be deleted. In order to achieve this, the respective extensions is left empty. It is important to always send the complete block when updating.
Delete .jobs extension
<jobs:contact xmlns:jobs="urn:org:domainrobot:ns:contact:jobs-1.0"> <jobs:adminType>0</jobs:adminType> <jobs:contactTitle>JOBS_CONTACT_TITLE</jobs:contactTitle> <jobs:hrMember>0</jobs:hrMember> <jobs:website/> </jobs:contact>
Delete all contact extensions
All extensions are to be removed for the extensions of the TLD .jobs. The respective block must be left empty.
Delete .jobs extension
<jobs:contact xmlns:jobs="urn:org:domainrobot:ns:contact:jobs-1.0"/>