Used to register a new domain name
For more information about DNS zone operations and the interactions with domains see our Knowledge Base.
| Name | Type | Description | Restrictions |
|---|---|---|---|
| domainName | String | The domain name |
|
| Name | Type | Required / Optional | Description | Restrictions |
|---|---|---|---|---|
| quote | Boolean | Optional | If true, validate the request and request a quote for the action |
| Name | Type | Required / Optional | Description | Restrictions |
|---|---|---|---|---|
| customer | String | Required | The customer handle |
|
| registrant | String | Required | The handle of the contact to use as registrant |
|
| privacyProtect | Boolean | Optional | If set to True, privacy protect will be enabled, defaults to the 'Privacy Protect' setting in your account | |
| period | Integer | Optional | The initial registration period for the domain name in months, defaults to the minimum period allowed by the registry | |
| authcode | String | Optional | The auth code for the domain name |
|
| languageCode | String | Optional | For IDN domains, the TLD specific language code for the domain name |
|
| autoRenew | Boolean | Optional | If set to False, the domain will not be auto renewed upon expiration, defaults to True | |
| ns | List <String> | Optional | List of name servers to use for the domain name |
|
| skipValidation | Boolean | Optional | If set to True, contact validation will not be started. If validation is required before activation the domain will not be activated and get the PENDING_VALIDATION status. The domain will automatically be activated if validation is completed at a later time. This option cannot be used for TLD's that require pre validation. | |
| launchPhase | String | Optional | The launch phase the domain is to be registered in, this field is only required if the TLD is not in General Availability yet |
|
| zone | zone | Optional | DNS template to use for the domain name, transform an existing zone of the specified service into a managed zone or creates a new managed zone if not found. Vanity name servers can be specified on the "ns" field. |
|
| contacts | List < contacts > | Optional | Domain contacts and their role | |
| keyData | List < keyData > | Optional | DNSSEC Key data for domain | |
| billables | List < billables > | Optional | Acknowledgment of billables for this request |
| Name | Type | Required / Optional | Description | Restrictions |
|---|---|---|---|---|
| service | Enum | Optional | DNS service to provision, defaults to BASIC |
Possible values:
|
| template | String | Optional | In case of a new zone, the template to use |
|
| link | Boolean | Optional | Unless false, the zone is linked to the template | |
| master | String | Optional | In case of a new zone, the IP address of the (hidden) master |
|
| dnssec | Boolean | Optional | In case of a new zone, provision zone with DNSSEC |
| Name | Type | Required / Optional | Description | Restrictions |
|---|---|---|---|---|
| protocol | Integer | Required | The DNSSEC protocol |
Possible values:
|
| flags | Integer | Required | The DNSSEC flags |
Possible values:
|
| algorithm | Integer | Required | The DNSSEC algorithm |
Possible values:
|
| publicKey | String | Required | The base64 encoded public key |
|
| Name | Type | Required / Optional | Description | Restrictions |
|---|---|---|---|---|
| product | String | Required | The product |
|
| action | Enum | Required | The action |
Possible values:
|
| quantity | Integer | Optional | The maximum quantity, default 1 |
| Name | Type | Required / Optional | Description |
|---|---|---|---|
| domainName | String | Required | The domain name |
| expiryDate | Timestamp | Optional | The expiry date of the created domain name |
| status | List <Enum> | Optional |
Possible values:
|
| Name | Type | Required / Optional | Description |
|---|---|---|---|
| domainName | String | Required | The domain name |
| expiryDate | Timestamp | Optional | The expiry date of the created domain name |
| status | List <Enum> | Optional |
Possible values:
|
Besides the generic errors these specific error responses can be expected.
| Type | Status | Description |
|---|---|---|
| BillableAcknowledgmentNeededException | 400 Bad Request |
POST
/v2/domains/domainName
Content-Type: application/json
{}