Info reseller[Link]

Purpose

Allows the registrar to retrieve information about the current status of an existing reseller.

The structure of the command is according to the RFC.

  • <org:id> is required. Contains the unique identifier of the reseller chosen by the registrar.

Information for only one reseller can be retrieved within the same command.

Please refer to the examples to see a complete request.

Examples[Link]

A info reseller command looks like:

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
  <command>
    <info>
      <org:info xmlns:org="urn:ietf:params:xml:ns:epp:org-1.0">
        <org:id>reseller01</org:id>
      </org:info>
    </info>
  </command>
</epp>

The EPP server responds with the information for that reseller:

<?xml version="1.0" encoding="UTF-8"?>
<epp xmlns="urn:ietf:params:xml:ns:epp-1.0" xmlns:org="urn:ietf:params:xml:ns:epp:org-1.0">
  <response>
    <result code="1000">
      <msg>Command completed successfully</msg>
    </result>
    <resData>
      <org:infData>
        <org:id>reseller01</org:id>
        <org:roid>t1-dns-be-82</org:roid>
        <org:role>
          <org:type>reseller</org:type>
          <org:status>ok</org:status>
        </org:role>
        <org:status>ok</org:status>
        <org:postalInfo type="loc">
          <org:name>My first Reseller</org:name>
        </org:postalInfo>
        <org:url>https://www.the-reseller-company.be</org:url>
        <org:clID>t1-dns-be</org:clID>
        <org:crID>t1-dns-be</org:crID>
        <org:crDate>2022-03-18T13:44:16.752Z</org:crDate>
      </org:infData>
    </resData>
    <trID>
      <svTRID>dnsbe-0</svTRID>
    </trID>
  </response>
</epp>