This document describes the specifications for the registration and maintenance of domains on MySRS using the MySRS API. Through the API, the domain resellers or registrars, which from here on will be collectively referred to as partners, can create their own software tools that talk to MySRS and automate the following domain service procedures, called requests:

1. Determine if a domain has been registered;
2. Query MySRS for domain/transaction information;
3. Buy a domain; and
4. Manage a domain (like renew a domain, edit a domain's contact info, etc.)

The MySRS System has no notion of state. Every request to the server is expected to be independent of other requests.

The term domain is used in this document to refer to second level .nz domains.

Examples show the XMLINPUT/Request, which are XML messages sent by the partner's client, and XMLOUTPUT/Response, which is the response sent back by the MySRS API server. The terms "System", "Server" and "backend" are used in this document to refer to the MySRS API server.

SSL

It is not recommended to send requests in clear text, since requests contains partner-sensitive information, such as the partner's user identifier and password. Requests should be sent via SSL.

Testing

All partners are provided access to our test registration system.

To access the test system, the partner's automation tool should do an HTTP POST to the URL shown below and send a request XML with the default test account's userid and password in the request XML header.

URL: https://mysrstest.domains.ph/cgi-bin/phbackend.pl
userid: i-register
password: i-register1

The XML format for requests and responses are specified in the Request and Response Format page.

The test system and the live production system access different databases. A domain name that exists in the live system's database may or may not be present in the test system's. You will not be billed for the domain names registered in the test system, because these domain names will not be propagated to the zone file.