From HEXONET Wiki
(Created page with "{{#repositoryinfo: PRO-LIVE-1API | pro }} {{Sidebar}} {{#var:ABOUTTLD}} <br><br> = Registry = {{Summarybox | Registry={{#IfEmpty: {{#var:REGISTRYURL}} | [{{#var:REGISTRY...") |
|||
| Line 165: | Line 165: | ||
= TLD specific = | = TLD specific = | ||
| − | {{ | + | === Domain Limitations and Requirements === |
| + | {{warnbox | You have to create an A/V record after registering a 2nd or 3rd level resolving .PRO domain. We automatically request the URL that you need in order to complete your A/V record on the registry website. As long as you do not complete the data for the A/V record, the domain is inactive and does not resolve. You can access the URL by using the [[API:StatusDomain|StatusDomain]] command. Please note that it might take a few minutes until the registry issues the URL. Furthermore the property X-PRO-INACTIVE indicates whether a domain name is still inactive.}} | ||
| + | {{warnbox | You have to specify at least 2 nameservers for a .PRO domain to become active.}} | ||
| + | = Addons = | ||
| + | |||
| + | {{#var:DOMAINADDONTABLE}} | ||
| + | |||
| + | = RegistrarOC = | ||
| + | |||
| + | {{#var:REGISTRAROCSENTENCE}} | ||
| + | |||
| + | {{#var:CATEGORY}} | ||
| + | |||
| + | === RegistrarOC specific parameters === | ||
| + | |||
| + | As the owner of a .PRO repository you do not have to provide the following extension: | ||
| + | |||
| + | <div id="parameter">X-PRO-ACCEPT-TOU</div> = 0 | 1 ''Optional'' | ||
| + | |||
| + | ==== Completing the A/V data ==== | ||
| + | |||
| + | Besides the possibility that you may request the URL that allows your customer to complete the A/V data at the registry website we can also configure your account to automatically request this URL. Alternatively, you can submit the A/V data using the API specifying '''all''' of the following parameters with the [[API:AddDomainAvRecord|AddDomainAvRecord]] command: | ||
| + | |||
| + | <div id="parameter">PROFESSIONTYPE</div> = <TEXT>: identifier for the profession of the license<br/> | ||
| + | <div id="parameter">JURISDICTIONCOUNTRY</div> = <COUNTRY>: the ISO country code within which the license has been issued<br/> | ||
| + | <div id="parameter">LICENSEAUTHORITY</div> = <TEXT>: the licensing authority that issued the license (this can be a state or province, or it can be the full name of the licensing authority)<br/> | ||
| + | <div id="parameter">LICENSENUMBER</div> = <TEXT>: the license number<br/> | ||
| + | <div id="parameter">LICENSEDATE</div> = <TEXT>: the date the license was issued<br/> | ||
| + | <div id="parameter">FIRSTNAME</div> = <TEXT>: the first name of the person to which the license was issued<br/> | ||
| + | <div id="parameter">LASTNAME</div> = <TEXT>: the family name of the person to which the license was issued<br/> | ||
| + | <div id="parameter">BIRTHDATE</div> = <TEXT>: the date of birth of the professional<br/> | ||
| + | <div id="parameter">WEBSITE</div> = <TEXT>: the URL of the licensing authority that issued the license<br/> | ||
| + | |||
| + | '''In this case, it is not necessary to do the confirmation using the URL provided in the response.''' | ||
| + | |||
| + | |||
| + | |||
| + | For the [[API:AddDomainAvRecord|AddDomainAvRecord]] command you can submit additional extensions: | ||
| + | |||
| + | |||
| + | <div id="parameter">HOST</div> = <TEXT> (max. 255 chars) ''Optional'' | ||
| + | |||
| + | possible values: | ||
| + | |||
| + | '''registryTK-registryUI''' - Default value. The registrar will create an A/V object indicating a host type of RegistryTK-RegistryUI and indicating the ContactId of the registrant contact object. (The registrant contact is the link between a domain and an A/V object.) RegistryPro responds with a URL (containing the identifier of the A/V object) of the RegistryPro hosted A/V site, and the registrar refers the registrant to this site. RegistryPro collects and verifies the A/V data, then activates the domain. | ||
| + | |||
| + | '''registryTK-registrarUI''' - In the second option, RegistryPro also performs all the checks, but the registrar may provide the user interface for collecting the A/V data. The registrar, first, collects the A/V data directly from the registrant. The registrar, then, creates an A/V object indicating RegistryTK-RegistrarUI and includes the A/V data in the <create> request. Again, when creating the A/V object, the registrar should associate the object with the registrant contact of the domain being registered. There are no retries on professional data; if it doesn’t verify the A/V object is marked final and failed. If the professional verification succeeds, RegistryPro will automatically activate the domain name. | ||
| + | |||
| + | |||
| + | <div id="parameter"> CHECKTYPE</div>= <TEXT> (max. 255 chars) ''Optional'': The check type specifies what A/V data must be collected and verified in an A/V Check. Clients should set this parameter to a value appropriate to the purpose of the A/V object. This parameter currently supports only the following value: | ||
| − | |||
<headertabs/> | <headertabs/> | ||
Revision as of 11:30, 7 August 2012
| Registry |
- |
| Dispute Policy |
- |
| Limitations |
|
| Allowed number of NS |
to |
Domain Registration
Domains can be registered with the API AddDomain command.
command = AddDomain domain = (DOMAIN)
REQUIRED
ownercontact0 = (CONTACT) admincontact0 = (CONTACT) techcontact0 = (CONTACT) billingcontact0 = (CONTACT) nameserver0 = (NAMESERVER) nameserver1 = (NAMESERVER)
OPTIONAL
secdns-ds# = <LONGTEXT> | <NULL> secdns-key# = <LONGTEXT> | <NULL> secdns-maxsiglife = <INT> auth = <TEXT> | <NULL> host# = <TEXT> | <NULL> transferlock = 0 | 1 | <NULL> subuser = <TEXT> | <NULL> nameserverset = <TEXT> | <NULL>
Domain Transfer
There is a special procedure to handle a domain transfer. Please contact our Support-Team if you should need further information.
command = TransferDomain domain = (DOMAIN)
REQUIRED
auth = <TEXT> | <NULL> action = REQUEST | APPROVE | DENY | CANCEL | USERTRANSFER domainauth = <TEXT>
OPTIONAL
order = CREATE | REPLACE | UPDATE orderid = <INT> emaillanguage = <TEXT> emailurl = <TEXT> emaillanguage = <TEXT> emailtac = <TEXT> requestentity = <TEXT> emailsender = <TEXT> | <NULL> emailsubject = <TEXT> | <NULL> preconfirmed = <TEXT> transferconfirmationemailoverride = <EMAIL> | <NULL> nameserver# = <TEXT> | <NULL> host# = <TEXT> | <NULL> subuser = <TEXT> | <NULL> period = <PERIOD> x-idn-language = <TEXT> | <NULL> ownercontact0 = <CONTACT> | <NULL> admincontact0 = <CONTACT> | <NULL> techcontact0 = <CONTACT> | <NULL> billingcontact0 = <CONTACT> | <NULL> transferlock = 0 | 1 | <NULL> repository = <NULL> | <TEXT>
Delete Domain
Domains can be deleted with the API DeleteDomain command.
There is no Deletion Restorable Period.
command = DeleteDomain domain = (DOMAIN)
REQUIRED
n/a
OPTIONAL
domainalerttriggercode = <TEXT> | <NULL> repository = <TEXT> | <NULL>
Restore Domain
command = RestoreDomain domain = (DOMAIN)
REQUIRED
n/a
OPTIONAL
force = 0 | 1 | <NULL> renewalmode = <NULL> | <TEXT> subuser = <TEXT>
Ownerchange
Domain Limitations and Requirements
No special procedures.
RegistrarOC specific parameters
As the owner of a .PRO repository you do not have to provide the following extension:
Completing the A/V data
Besides the possibility that you may request the URL that allows your customer to complete the A/V data at the registry website we can also configure your account to automatically request this URL. Alternatively, you can submit the A/V data using the API specifying all of the following parameters with the AddDomainAvRecord command:
In this case, it is not necessary to do the confirmation using the URL provided in the response.
For the AddDomainAvRecord command you can submit additional extensions:
possible values:
registryTK-registryUI - Default value. The registrar will create an A/V object indicating a host type of RegistryTK-RegistryUI and indicating the ContactId of the registrant contact object. (The registrant contact is the link between a domain and an A/V object.) RegistryPro responds with a URL (containing the identifier of the A/V object) of the RegistryPro hosted A/V site, and the registrar refers the registrant to this site. RegistryPro collects and verifies the A/V data, then activates the domain.
registryTK-registrarUI - In the second option, RegistryPro also performs all the checks, but the registrar may provide the user interface for collecting the A/V data. The registrar, first, collects the A/V data directly from the registrant. The registrar, then, creates an A/V object indicating RegistryTK-RegistrarUI and includes the A/V data in the <create> request. Again, when creating the A/V object, the registrar should associate the object with the registrant contact of the domain being registered. There are no retries on professional data; if it doesn’t verify the A/V object is marked final and failed. If the professional verification succeeds, RegistryPro will automatically activate the domain name.
