To start an EPP Gateway session, the client must send a “login” command using valid credentials. An EPP Gateway session is closed by sending a “logout” command or simply by closing the TCP connection. After an initial greeting, clients can always query the Gateway by sending a “hello” command.
1. Hello command
An EPP client MAY request a from the EPP server at any time. Often this command is used for checking the status of the EPP server.
EPP Gateway command request/response:
|
1 2 3 4 5 |
<?xml version="1.0" encoding="UTF-8" standalone="no"?> <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> <hello></hello> </epp> |
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 |
<?xml version="1.0" encoding="UTF-8" standalone="no"?> <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> <greeting> <svID>ST Registry EPP server epp-api.sandbox.registry.st</svID> <svDate>2014-06-19T14:46:07+02:00</svDate> <svcMenu> <version>1.0</version> <lang>en</lang> <objURI>urn:ietf:params:xml:ns:domain-1.0</objURI> <objURI>urn:ietf:params:xml:ns:contact-1.0</objURI> <objURI>urn:ietf:params:xml:ns:host-1.0</objURI> <svcExtension> <extURI>urn:ietf:params:xml:ns:domainsCollection-1.0</extURI> <extURI>urn:ietf:params:xml:ns:whoisPrivacy-1.0</extURI> <extURI>urn:ietf:params:xml:ns:registrar-1.0</extURI> </svcExtension> </svcMenu> <dcp> <access> <all></all> </access> <statement> <purpose> <admin></admin> <prov></prov> </purpose> <recipient> <ours></ours> <public></public> </recipient> <retention> <stated></stated> </retention> </statement> </dcp> </greeting> </epp> |
2. Login command
An EPP Gateway session must be established before any operations can be sent to the gateway. Additionally, EPP limits login ID to a maximum of 16 characters.
EPP Gateway command request/response:
|
1 2 3 4 5 6 7 8 9 10 11 |
<?xml version="1.0" encoding="UTF-8" standalone="no"?> <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> <command> <login> <clID>login</clID> <pw>password</pw> </login> <clTRID>53a2dc350dec6</clTRID> </command> </epp> |
|
1 2 3 4 5 6 7 8 9 10 11 12 |
<?xml version="1.0" encoding="UTF-8" standalone="no"?> <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> <response> <result code="1000"> <msg>Command completed successfully</msg> </result> <trID> <clTRID>53a2dc350dec6</clTRID> <svTRID>e802eec5-67bc-492b-90c0-ec2a4adf90af</svTRID> </trID> </response> </epp> |
3. Logout command
An EPP Gateway session in general should be must closed with the “Logout” command after all instructions are complete, unless for performance reasons you wish to keep the connection open. Please remember that the connection is automatically closed when the TCP timeout occurs or the TCP session is closed.
EPP Gateway command request/response:
|
1 2 3 4 5 6 7 8 |
<?xml version="1.0" encoding="UTF-8" standalone="no"?> <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> <command> <logout></logout> <clTRID>53a2e02c46ddd</clTRID> </command> </epp> |
|
1 2 3 4 5 6 7 8 9 10 11 12 |
<?xml version="1.0" encoding="UTF-8" standalone="no"?> <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> <response> <result code="1500"> <msg>Command completed successfully; ending session</msg> </result> <trID> <clTRID>53a2e02c46ddd</clTRID> <svTRID>53a2e4cb46bf9</svTRID> </trID> </response> </epp> |
