From HEXONET Wiki
(Created page with "CoreAPI") |
|||
| Line 1: | Line 1: | ||
| − | + | __NOTOC__ | |
| + | <h2>API access</h2> | ||
| + | |||
| + | These are the current methods of getting access to the HEXONET system: | ||
| + | |||
| + | <b> | ||
| + | [[HTTpS|HTTP / HTTPS]] | ||
| + | [[HighPerformanceProxySetup|High Performance Proxy Setup (using Apache2's proxy module)]] | ||
| + | |||
| + | [[EPp|EPP]] | ||
| + | [[NetDri|EPP access using the Net::DRI perl library]] | ||
| + | |||
| + | [[MailRobot|MAILROBOT]] | ||
| + | |||
| + | [[SoAp|SOAP/XMLRPC]] | ||
| + | |||
| + | </b> | ||
| + | |||
| + | Download: {{Template:Pdf|SMTP_Gateway.pdf| SMTP-Gateway}} | ||
| + | |||
| + | Download: {{Template:Pdf|SOAP_Gateway.pdf| SOAP-Gateway}} | ||
| + | |||
| + | Download: {{Template:Pdf|XMLRPC_Gateway.pdf| XMLRPC-Gateway}} | ||
| + | |||
| + | |||
| + | <h2>Base URL</h2> | ||
| + | |||
| + | The base url, in order to connect to our system is '''https://api.ispapi.net/api/call.cgi''' | ||
| + | |||
| + | The base url, in order to connect to our OT&E (Testbed System) is: https://api.ispapi.net/api/call.cgi?s_entity=1234 | ||
| + | |||
| + | |||
| + | <h2>Event management</h2> | ||
| + | |||
| + | |||
| + | A really important feature to track all domain-transactions. Normally you can poll all domain-events by using the commands: <b>[[StatusEvent|StatusEvent]]</b>, <b>[[QueryEventlist|QueryEventlist]]</b> and <b> [[DeleteEvent|DeleteEvent]]</b>. Alternatively you can use the option <b>[[EventsPop3|Receive Events over POP3]]</b>. Please note that you should always choose only one method to avoid inconstancies. | ||
| + | |||
| + | |||
| + | HEXONET informs you via email about all events via the <b> [[PushEvents|PushEvents]]</b> feature. PushEvents is an additional event messaging service to store and process all product-related events on your side. Inform your client about outgoing/incoming transfers, successful registrations and many more. It can also be used as a backup solution for your own security. | ||
| + | |||
| + | <h2>System API error codes</h2> | ||
| + | Please find below a list of all API - Error CODES: | ||
| + | * <b> [[API:ErrorCodes | API-ERROR CODES]]</b> | ||
| + | |||
| + | <h2>System usage restrictions</h2> | ||
| + | *<b>[[API:QuotaSystem | System Usage Restrictions (Quota Regulation)]]</b> | ||
| + | |||
| + | |||
| + | <h2>HEXONET Renewal System</h2> | ||
| + | |||
| + | The HEXONET Renewal System manages the lifecycle of an object, based on several parameters which are described briefly on the following pages: | ||
| + | |||
| + | * [[HEXONET Renewal System]] | ||
| + | * [[Manual Domain Renewals]] | ||
| + | |||
| + | |||
| + | <h1>API commands</h1> | ||
| + | |||
| + | |||
| + | |||
| + | |||
| + | Download: {{Template:Pdf|CORE_API_Reference.pdf| Core API}} | ||
Revision as of 12:48, 28 August 2012
API access
These are the current methods of getting access to the HEXONET system:
HTTP / HTTPS High Performance Proxy Setup (using Apache2's proxy module)
EPP EPP access using the Net::DRI perl library
Download: SMTP-Gateway
Download: SOAP-Gateway
Download: XMLRPC-Gateway
Base URL
The base url, in order to connect to our system is https://api.ispapi.net/api/call.cgi
The base url, in order to connect to our OT&E (Testbed System) is: https://api.ispapi.net/api/call.cgi?s_entity=1234
Event management
A really important feature to track all domain-transactions. Normally you can poll all domain-events by using the commands: StatusEvent, QueryEventlist and DeleteEvent. Alternatively you can use the option Receive Events over POP3. Please note that you should always choose only one method to avoid inconstancies.
HEXONET informs you via email about all events via the PushEvents feature. PushEvents is an additional event messaging service to store and process all product-related events on your side. Inform your client about outgoing/incoming transfers, successful registrations and many more. It can also be used as a backup solution for your own security.
System API error codes
Please find below a list of all API - Error CODES:
System usage restrictions
HEXONET Renewal System
The HEXONET Renewal System manages the lifecycle of an object, based on several parameters which are described briefly on the following pages:
API commands
Download: Core API
