Table of Contents

Function

The DomainPreregCreate task starts the preregistration for a domain.
If "PENDING" is specified as the "status", the newly created preregistration is also confirmed immediately (see DomainPreregConfirm).
Alternatively, you can use the path "/domainPrereg/_confirm" in JSON to confirm the preregistration.

Note that the preregistration phases of each new TLD are limited in time by the regulations of the respective registry.

Description

Route: POST ​/domainPrereg

Request 
{
    "name": "example.web",   
	"tmchMark": {
		"reference": "0000061236-1"
	},
	"status": "OPEN",
	"phase": "live",         
	"nameServers": [
    	{
        	"name": "ns1.example.com"
		},
        {
        	"name": "ns2.example.com"
		}
	]
}
Response 
{
    "stid": "20210826-app-94855",
    "status": {
        "code": "S0110001",
        "text": "The domain has been preregistered successfully.",
        "type": "SUCCESS"
    },
    "object": {
        "type": "DomainPrereg",
        "value": "example.web",
        "data": {
            "name": "example.web",
            "orderReference": "4610d83c-597f"
        }
    }
}

Task code: 0110001
Uses Domain_Prereg object

Request 
<request>
	<auth>
		<user>user</user>
		<password>password</password>
		<context>4</context>
	</auth>
	<task>
		<code>0110001</code>
		<domain_prereg>
			<name>example.web</name>
			<tmch_mark>
				<reference>0000061236-1</reference>
			</tmch_mark>
			<phase>live</phase>
			<status>open</status>
			<nserver>
				<name>ns1.example.com</name>
			</nserver>
			<nserver>
				<name>ns2.example.com</name>
			</nserver>
		</domain_prereg>
		<reply_to>customer@example.com</reply_to>
	</task>
</request>
Response 
<response>
	<result>
		<data/>
		<status>
			<code>S0110001</code>
			<text>The domain has been preregistered successfully.</text>
			<type>success</type>
			<object>
				<type>domain_prereg</type>
				<value>30902702-0c7c</value>
			</object>
		</status>
	</result>
	<stid>20131202-app-3335</stid>
</response>