All contact commands: (check) (create) (delete) (info) (modify)
To create a contact object you need to use the contact:create command. A long list of attributes can be associated with the new contact.
Please note that although the contact:authInfo (password) must be specified on the contact create, it is useless, because contacts do not use authinfo for information or transfer. It is only mandatory because the EPP RFC specifies that it must be set.
<?xml version="1.0" encoding="UTF-8"?>
<epp xmlns="urn:ietf:params:xml:ns:epp-1.0" xmlns:contact="urn:ietf:params:xml:ns:contact-1.0">
<command>
<create>
<contact:create>
<contact:id>MRG57c42c1b84979</contact:id>
<contact:postalInfo type="int">
<contact:name>Contact name</contact:name>
<contact:org>Contact organization</contact:org>
<contact:addr>
<contact:street>Street</contact:street>
<contact:city>City</contact:city>
<contact:sp>PR</contact:sp>
<contact:pc>10000</contact:pc>
<contact:cc>US</contact:cc>
</contact:addr>
</contact:postalInfo>
<contact:voice>+31.612345678</contact:voice>
<contact:email>test@test.com</contact:email>
<contact:authInfo>
<contact:pw>5UZF4CL4BK</contact:pw>
</contact:authInfo>
</contact:create>
</create>
<clTRID>57c42c1b8491e</clTRID>
</command>
</epp>
Please note that although you can specify <contact:id> on the request, it is not actually used. The actually created contact id is returned in the response when the create was succesful
The response from the server lists the contact ID of the newly created contact, and the date/time of creation. Please store this contact ID for later reference if you want to use it in the creation or modification of a domain name.
<?xml version="1.0" encoding="UTF-8"?>
<epp xmlns="urn:ietf:params:xml:ns:epp-1.0" xmlns:contact="urn:ietf:params:xml:ns:contact-1.0">
<response>
<result code="1000">
<msg>Command completed successfully</msg>
</result>
<resData>
<contact:creData>
<contact:id>RP01mGXpAB6Ph8hmArSu6P9a></contact:id>
<contact:crDate>2016-08-29T12:35:39.670369+0000></contact:crDate>
</contact:creData>
</resData>
<trID>
<svTRID>MTR_a34e6724699ac76ec241e169737d578778555d7d</svTRID>
<clTRID>57c42c1b8491e</clTRID>
</trID>
</response>
</epp>