XML Template for int.vn domains

XML Template - Updating the organisational contact

<?xml version="1.0" encoding="UTF-8"?>
    <request
        xmlns:domain="http://www.eurodns.com/domain"
        xmlns:contact="http://www.eurodns.com/contact">

        <domain:trade>
            <domain:name>#DOMAIN.TLD#</domain:name>
        </domain:trade>

        <contact:update>
            <contact:type>org</contact:type>
            <contact:contactprofileid>#CONTACT PROFILE ID#</contact:contactprofileid>
            <contact:firstname>#FIRSTNAME#</contact:firstname>
            <contact:lastname>#LASTNAME#</contact:lastname>
            <contact:company>#COMPANY#</contact:company>
            <contact:address1>#ADDRESS LINE 1#</contact:address1>
            <contact:address2>#ADDRESS LINE 2#</contact:address2>
            <contact:address3>#ADDRESS LINE 3#</contact:address3>
            <contact:city>#CITY#</contact:city>
            <contact:zipcode>#ZIP/POSTAL CODE#</contact:zipcode>
            <contact:country_code>#COUNTRY CODE#</contact:country_code>
            <contact:email>#EMAIL ADDRESS#</contact:email>
            <contact:phone>#PHONE NUMBER#</contact:phone>
            <contact:fax>#FAX NUMBER#</contact:fax>
        </contact:update>

        <extension:create>
            <extension:data tld="int.vn">
                <extension:registry>
                    <registry:a_idpp>#A_IDPP#</registry:a_idpp>
                    <registry:a_birthdate>#A_BIRTHDATE#</registry:a_birthdate>
                    <registry:a_gender>#A_GENDER#</registry:a_gender>
                    <registry:admin_type_cpy_id>#ADMIN_TYPE_CPY_ID#</registry:admin_type_cpy_id>
                    <registry:b_idpp>#B_IDPP#</registry:b_idpp>
                    <registry:b_birthdate>#B_BIRTHDATE#</registry:b_birthdate>
                    <registry:b_gender>#B_GENDER#</registry:b_gender>
                    <registry:billing_type_cpy_id>#BILLING_TYPE_CPY_ID#</registry:billing_type_cpy_id>
                    <registry:o_iddocument extension="#EXTENSION#">#O_IDDOCUMENT#</registry:o_iddocument>
                    <registry:o_idpp>#O_IDPP#</registry:o_idpp>
                    <registry:o_birthdate>#O_BIRTHDATE#</registry:o_birthdate>
                    <registry:o_gender>#O_GENDER#</registry:o_gender>
                    <registry:registrant_type_cpy_id>#REGISTRANT_TYPE_CPY_ID#</registry:registrant_type_cpy_id>
                    <registry:registrant_type_cpy_name>#REGISTRANT_TYPE_CPY_NAME#</registry:registrant_type_cpy_name>
                    <registry:registrant_type_cpy_type>#REGISTRANT_TYPE_CPY_TYPE#</registry:registrant_type_cpy_type>
                    <registry:tech_type_cpy_id>#TECH_TYPE_CPY_ID#</registry:tech_type_cpy_id>
                </extension:registry>
            </extension:data>
        </extension:create>
    </request>

<domain:trade> (Occurrences: 1)

R

#DOMAIN.TLD#

Domain to be traded

<contact:update> (Occurrences: 1)

Note: Only the organisational contact can be updated

R	#PRIORITY#	Priority of the nameserver (1-12)
R	#FULLY QUALIFIED DOMAIN NAME#	Fully qualified domain name of the nameserver
R	#IP ADDRESS#	IPv4 address of the nameserver

<contact:create> (Occurrences: 4)

Note: The four contacts admin, billing, tech, org have to be specified.

O	#CONTACT PROFILE ID#	Use a contact profile instead of specifying the contact details
R	#FIRSTNAME#	Firstname
R	#LASTNAME#	Lastname
O	#COMPANY#	Company
R	#ADDRESS LINE 1#	Address, Line 1
O	#ADDRESS LINE 2#	Address, Line 2
O	#ADDRESS LINE 3#	Address, Line 3
R	#CITY#	City
R	#ZIP/POSTAL CODE#	ZIP/Postal code
R	#COUNTRY CODE#	Country code (ISO 3166-1-alpha-2)
R	#EMAIL ADDRESS#	Email address
R	#PHONE NUMBER#	Phone number format: +999999999. Starting with +country phone code
O	#FAX NUMBER#	Phone number format: +999999999. Starting with +country phone code

<extension:create>

R	#A_IDPP#	Administrative contact Identification or Passport Number (between 2 and 50 characters)
R	#A_BIRTHDATE#	Administrative contact birthdate (YYYY-MM-DD)
R	#A_GENDER#	Administrative contact Gender
R	#ADMIN_TYPE_CPY_ID#	Admin Identity
R	#B_IDPP#	Billing contact Identification or Passport Number (between 2 and 50 characters)
R	#B_BIRTHDATE#	Billing birthdate
R	#B_GENDER#	Billing gender
R	#BILLING_TYPE_CPY_ID#	Billing Identity
R	#O_IDDOCUMENT#	Document should be sent in base64.
R	#EXTENSION#	Document extension ("png", "jpg", "jpeg", "gif", "pdf", "smd", "doc", "docx")
R	#O_IDPP#	Registrant contact Identification or Passport Number (between 2 and 50 characters)
R	#O_BIRTHDATE#	Registrant contact birthdate (YYYY-MM-DD)
R	#O_GENDER#	Registrant contact Gender
R	#REGISTRANT_TYPE_CPY_ID#	Company Registration Number
R	#REGISTRANT_TYPE_CPY_NAME#	Company name
R	#REGISTRANT_TYPE_CPY_TYPE#	Company type (INC, LTD, SARL, GMBH ....)
R	#TECH_TYPE_CPY_ID#	Tech Identity

The following request is an example on how to perform a trade by using a contact profile instead of specifying the complete contact details in the request.

XML Example 1 - Perform a trade by using a contact profile

<?xml version="1.0" encoding="UTF-8"?>
    <request
        xmlns:domain="http://www.eurodns.com/domain"
        xmlns:contact="http://www.eurodns.com/contact">
        <domain:trade>
            <domain:name>eurodns.com</domain:name>
        </domain:trade>
        <contact:update>
            <contact:type>org</contact:type>
            <contact:contactprofileid>123456</contact:contactprofileid>
        </contact:update>
    </request>

If our server accepts the request, the following code will be returned:

<?xml version="1.0" encoding="UTF-8"?>
    <response xmlns="http://www.eurodns.com/">
        <result code="1001">
            <msg>Command completed successfully, action pending</msg>
        </result>
    </response>

Legend

O	The element is optional and does not have to be specified in the request and/or answer
R	The element is mandatory and has to specified in the request and/or answer