The EPP interface documentation - version '1.0.1'

EPP XML schemas:

Updated: 2012-08-21 (rev. 1.0 to 1.0.1): Extensions to support electronic applicant statements sent over EPP by use of a new 'applicantDataset' attribute. The extensions are found in the new schema file 'no-ext-domain-1.1.xsd'.

These XML schemas formally define the layout and contents of the EPP interface commands and attributes, and must be studied carefully and used in client implementations.

The schemas are put in an archive file for convenient and consistent downloads. You can select from either a zip or a gz archive:

• EPP XML schemas-1.0.1.no.zip
• EPP XML schemas-1.0.1.no.tar.gz

EPP Interface specification and description document

Updated: 2012-08-21 (rev. 2e2 to 3p3: Extensions to support the electronic applicant statements as defined in the '1.0.1' schemas. Various improvements and corrections. See 'Document History' in the document for details.

This document must be read by everyone who will implement client side software. It describes the various interface details in more detail, like the various .no schema extensions and the special business procedures.

• EPP_Interface_Specification.3p3.pdf

EPP interface error codes

Updated 2013-01-02: Error codes valid for the release on this date.

The EPP interface uses a number of extended error codes. These are documented on the error messages web page.

Constants and system limitations in the EPP system

Updated 2012-08-31: Added description of the limitations for electronic applicant declarations.
Released 2012-08-16: New page.

The EPP interface and the registry system is configuarable. Among other things, a number of constants are used to regulate what is allowed in some EPP operations. The values of the constants and a description of their usage is presented on a separate constants and system limitations web page.

EPP XML Example Sequences

Here a number of practical EPP XML sequences are supplied. These are informal only, intended to show how things could look in a real implementaton. The sequences should be studied carefully as they reveal how to interpret the XML schemas.

If a certain command or command sequence is not covered, you can use the Norid EPP client towards our test system to create the sequence. Just log in and perform the command or sequence in question. Afterwards, inspect the client's 'EPP protocol logs', via the 'Options' menu, to see the actual EPP XML sequences exchanged.