From HEXONET Wiki
These commands are required to manage your domain names e.g. Common domain commands, Host/Nameserver commands, Contact commands, Domain registry specific commands, Domain transfers, Branding, Control-Panel.
Domain API Quick-Find Downloads
HEXONET offers access to the domain-robot via a real EPP 1.0 (Extensible Provisioning Protocol) strict to RFC 4930-4933. EPP is the recommended RFC 4930-4933 communication-protocol between Domain-Registars and the respective Registries. With this EPP Implementation you now have access to hundreds of TLDs through one single protocol. In the event that you hold own accreditations then you now also have the possibility of managing your own accreditations through RegistrarOC and connect to them through EPP.
Download: EPP Manual with further information and EPP examples.
See also: EPP access using the Net::DRI perl library We also provide an EPP Demonstrator where you can easily execute EPP commands in our OT&E environment.
EPP Gateway Information
|EPP production environment||EPP Testbed / OTE|
|Login:||Your Username||Your Username|
|Password:||Your Password||Your Password|
HTTP / HTTPS
- The base url is https://api.ispapi.net/api/call.cgi
- The base url for OT&E (Testbed System) is: https://api.ispapi.net/api/call.cgi?s_entity=1234
- High Performance Proxy Setup (using Apache2's proxy module)
All API commands can be executed via email templates sent to email@example.com. firstname.lastname@example.org will also be the sender email address of HEXONET´s API call answers. To send emails to the API in OT&E mode, please use email@example.com as recipient address. Please note that you first have to create an OT&E account before you start with testing. Get your OT&E account now!
Download: SMTP-Gateway Your login credentials and the API command which should be executed has to be submitted in the message body. Further you can submit some kind of transaction ID in the subject line. The HEXONET system will pass this subject to the response email.
Example of an email to register a domain
s_login = login.id s_pw = secret_password s_user = subuser.id [COMMAND] command = AddDomain domain = reseller.com ownercontact0 = (CONTACT) admincontact0 = (CONTACT) techcontact0 = (CONTACT) billingcontact0 = (CONTACT) ... nameserver0 = ns1.yournameserver.com ... nameserver12 = ns13.yournameserver.com EOF
This Realtime SOAP Gateway has been developed to provide an easy way to connect existing shopping cart and domain ordering systems to a user account of our system. The gateway consists of a SOAP server that accepts XML requests conforming to a defined syntax and converts them into API calls. All incoming SOAP requests are processed immediately and a XML response is generated and returned to the client.
Download: SOAP-Gateway manual
Download: XMLRPC-Gateway manual As we only offer two SOAP methods: ping for testing, xcall for XIRCA requests, we do not provide a public WSDL file. All XIRCA commands can be obtained in the respective manuals.
SOAP HTTP call parameters:
Server-/Proxy-URL: "http(s)://18.104.22.168:8080" (use Port 8082 for SSL access) Namespace/URI: "urn:Api" available Methods: “echo” / “xcall”
SOAP HTTPS (SSL) call parameters:
Server-/Proxy-URL: "http://22.214.171.124:8082" Namespace/URI: "urn:Api" available Methods: “echo” / “xcall”
To access the OTE-system please simply specify the API parameter "s_entity=1234" to your request.
This Realtime XML-RPC Gateway has been developed to provide an easy way to connect existing shopping cart and domain ordering systems to a user account of our system. The gateway consists of a XML-RPC server that accepts XML requests conforming to a defined syntax and converts them into API calls. All incoming XML-RPC requests are processed immediately and a XML response is generated and returned to the client.
XML-RPC HTTP call parameters: IP: 126.96.36.199 Port: 8081 Server-/Proxy-URL: "http://188.8.131.52:8081" available Methods: “Api.echo” / “Api.xcall” XML-RPC HTTPS (SSL) call parameters: IP: 184.108.40.206 Port: 8083 Server-/Proxy-URL: "http://220.127.116.11:8083" available Methods: “Api.echo” / “Api.xcall” To access the OTE please simply specify the API parameter "s_entity=1234" to your request.