Below is the interface documentation necessary for providers who want to develop their own EPP client.
Current version: 1.0.2
Specifications for EPP interface, version 1.0.2
|EPP XML schema|
2014-12-02 (rev. 1.0.1 to 1.0.2): Added secdns-1.1.xsd, which is the standard schema for DNSSEC.
These XML schemas define layouts and content for commands and attributes in the EPP interface. They must be studied carefully and applied in the client implementation.
The schemas are in an archive file to make downloads simple and consistent. Choose either ZIP or GZ archive.
Download EPP-XML-Schemas-1.0.2 (ZIP, 15KB)
Download EPP-XML-Schemas-1.0.2 (GZ, 8KB)
|EPP interface specifications and description|
2019-11-08 (rev. 1e1): Minor changes and corrections. See Document History in the document for details.
This document must be read by all parties planning to implement a client application. It describes interface details, extensions made for .no and special business processes.
Download EPP_Interface_Specification.1e1.(PDF, 851KB)
|Error codes in the EPP interface|
2018-03-13: Error codes that apply to this release (new data model).
An expanded set of error codes are exchanged over the EPP interface.
The error codes are documented in detail on a separate error message page.
|EPP system constants and system limitations|
2018-05-05: Number of relations set to 0, and no dedicated admin/legal contact — these are adjustments in accordance with new data model.
2014-11-18: Value for Maximum number of organizations a person or role contact can be associated with increased from 10 to 20.
2014-01-29: Description of limits for DNSSEC parameters added.
EPP interface and registration system are configurable. Among other things, constants regulate what is permitted for some EPP operations.
The value of these constants and a description of how they are used is documented on a separate web page on constants and system limitations.
Example sequences with EPP/XML commands
|Example sequences with EPP/XML commands|
See page for example frequences for summary.
We show some practical examples of how XML sequences may look in an implementation (for information purposes only). These sequences should be studied carefully, as they illustrate how the XML schemas should be interpreted.
If a command or command sequence is not covered, you can use Norid’s EPP client against the test system to create the sequence. Log in and execute the command or command sequence you are interested in. The complete EPP XML sequence will then be available in the client’s log, which can be inspected via EPP protocol logs in the Options menu.
Example sequences are available here.