The Meta Registry Application Layer is the software kernel responsible for all registry/registrar/reseller transactions. It also performs the dispatching to the different registry handlers. It unifies all commands to a single set in order to handle all services.

Whenever a registry allows registration and management of domain names in real-time, EuropeanNIC supports these real-time specifications. To take full advantage, resellers should consider using one of our real-time protocols.

Resellers can connect to the Meta Registry through web interface or API . The different API gateways are EPP, XRRP, XML, SOAP, HTTPS and SMTP (E-Mail). All business operations through the Meta Registry are completely automated, allowing us to offer particularly favorable prices.

EPP (Extensible Provisioning Protocol)

RRP / XRRP

SOAP / XML-RPC

HTTPS socket

SMTP (E-Mail)

All processes via "Meta Registry" are completely automated, which enables you to offer specially attractive pricinag.

• EPP (Extensible Provisioning Protocol):

EuropeanNIC supports the EPP standard 1.0, the RFC 4930-4933 standards and the RCC 1.1 name space. We are able to use any existing EPP SDK to register international domain names. The EPP system translates the commands in real-time in the respective format used by the connected registries.

For accessing our EPP-system, please use the following connection-parameters:

# LIVE - system:
Host: epp.EuropeanNIC.net
Port: 700
# OT/E - system:
 Host: epp-ote.EuropeanNIC.net
 Port: 1700

Here an example of how the extensions must be set up:

<extension>
<keysys:create -xmlns:keysys="http://www.key-systems.net/epp/keysys-1.0">
    <keysys:domain>
      <keysys:it-pin>DE1234567912</keysys:it-pin>
    </keysys:domain>
  </keysys:create>
</extension>

• RRP / XRRP:

The eXtended Registry Registrar Protocol (XRRP) is a protocol for the registration and management of domain names and associated nameservers. XRRP is an improved version of the former RRP version (used by VeriSign to manage the .com, .net and .org zone).

[COMMAND]
command = checkDomain
domain = example.org
EOF
[RESPONSE]
code = 210
description = Domain name available
EOF

• SOAP / XML-RPC:

Access to the EuropeanNIC system is also possible with SOAP (Simple Object Access Protocol) and XML-RPC (Extensible Markup Language Remote Procedure Call). The modules are delivered in PERL and PHP languages.

Please set the parameter "s_opmode" to "OTE" to connect to our OT&E - environment.
For access using our SOAP - API, use the following connection - parameters:

Without SSL proxy => http://api.EuropeanNIC.net:8080/soap
With SSL proxy    => https://api.EuropeanNIC.net:8082/soap

Perl

For access with perl, we recommend using "SOAP::Lite", please have a look at the example below.

#!/usr/bin/perl -w
use SOAP::Lite; #+trace => debug;
use Data::Dumper;
my $soap = SOAP::Lite
     -> uri('urn:Api')
     -> proxy('https://api.EuropeanNIC.net:8082/soap')
;

my @commands = (
     {
          's_login' => 'demo',
          's_pw' => 'demoote',
          's_opmode' => 'OTE',
          'command' => 'CheckDomain',
          'domain' => 'example.com',
     },
);
my $res = $soap->xcall(@commands);
print Dumper($res->result) . "\n";

PHP

We recommend to use the PHP-internal SOAP - functions for accessing our SOAP - API with PHP. Please have a look at the example below.

<?php
$client = new SoapClient(NULL,
      array(
          "location" => "https://api.EuropeanNIC.net:8082/soap",
//        "location" => "http://api.EuropeanNIC.net:8080/soap",
          "uri" => "urn:Api",
          "style" => SOAP_RPC,
          "use" => SOAP_ENCODED,
     )
);
$params = array(
      array(
          -"s_login" => "demo",
          -"s_pw" => "demoote",
          -"s_opmode" => "OTE",
          -"command" => "CheckDomain",
          -"domain" => "example.com"
     -)
);
$result = $client->__call("xcall",
      $params,
      array(
          "uri" => "urn:Api",
          "soapaction" => "urn:Api#xcall")
);
print_r($result); ?>

• HTTPS socket:

You can also connect by using the following HTTP(s) call. The API commands are passed on through the parameters.

Connection data for the HTTPS - socket

# LIVE - URL
https://api.EuropeanNIC.net/api/call?s_login=demo&s_pw=demoote
# OT&E - URL
https://api.EuropeanNIC.net/api/call?s_opmode=OTE&s_login=demo&s_pw=demoote

If you do not add the parameter "s_opmode=OTE", you will connect to our live-system and may be charged for operations.

Wget

wget -nv "https://api.EuropeanNIC.net/api/call?
s_opmode=OTE&s_login=demo&s_pw=demoote&command=checkdomain&domain=example.org" -O

[RESPONSE]
code = 210
description = Domain name available
queuetime=0
runtime=0.054
EOF
2009-11-06 09:25:45 URL:https://api.EuropeanNIC.net/api/call?
s_opmode=OTE&s_login=demo&s_pw=demoote&command=checkdomain&domain=example.org [90] -> "" [1]

Curl

curl "https://api.EuropeanNIC.net/api/call?
s_opmode=OTE&s_login=demo&s_pw=demoote&command=checkdomain&domain=example.org"

[RESPONSE]
code = 210
description = Domain name not available
queuetime=0
runtime=0.15
EOF

• SMTP (E-Mail) Gateway:

The email gateway is a tool which enables resellers to register and administer domain names according to the “old standard” of InterNIC. This tool is reliable and is still used by many of our customers.

A basic "CheckDomain" command looks like the following:

s_login = demo
s_pw = demoote
s_opmode = OTE
[COMMAND]
command = CheckDomain
domain = example.com