Ascio Web Service v2

Registrant

The registrant class is only for registrant-contacts. It is not compatible with other contacts. Some parameters are different form contact-paramters, like the Name

PropertyDescriptionTLD-Kit
CreDate
Status
HandleThe Handle. Please don't use Handle and contact-data. The data won't be merged!
Example: "JD123"
3a
NamePlease enter firstname [space] lastname, or lastname, firstname as value. The name is part of social data. You need an owner-chage to change the name. The Name is required for every Registrant/Contact. (In case no handle is used)
Example: "ascio-is-great.com"
3b
OrgNameThe OrgName is part of social data. You need an owner-chage to change the OrgName.
Example: "Ascio"
3c
Address1The Address1 is required for every Registrant/Contact. (In case no handle is used)3d
Address2
CityThe City is required for every Registrant/Contact. (In case no handle is used)3e
State3g
PostalCodeThe PostalCode is required for every Registrant/Contact. (In case no handle is used)
Example: "888349"
3h
CountryCodeThe ISO 3166-1 code for the Country (DE,GB,DK,CH,SE,...). The CountryCode is required for every Registrant/Contact. (In case no handle is used)
Example: "DK"
3i
EmailThe Email is required for every Registrant/Contact. (In case no handle is used)
Example: "administrator@ascio-test-domain.com"
3l
PhonePhone number must be in E164a format, eg. +45.123456789 (no spaces, hyphens, etc.).
Example: "+45.123456789"
3j
FaxFax number must be in E164a format, eg. +45.123456789 (no spaces, hyphens, etc.)
Example: "+45.987654321"
3k
RegistrantTypeSome TLDs need a Registrant Type. In most cases this is used to specify which type of RegistrantNumber is used (e.G. VAT, Passboard ID)
Example: "C1"
3q
VatNumber3p
RegistrantDate3m
NexusCategory20b
RegistrantNumberAn ID of the Registrant. The RegistrantType may describe which type of ID is used.
Example: "abc123445"
3m
Details3s
WSDL for AWS v2
https://aws.demo.ascio.com/2012/01/01/AscioService.wsdl (OTE)
https://aws.ascio.com/2012/01/01/AscioService.wsdl (Live)
Please configure the IP-Whitelisting in the portal/demo-portal.