Info order
Queries information about already created order, identified by its id.
Orders are usually created by domain transform commands (create, update, renew, transfer and delete domain).
Input fields
- id - order id number (required)
Output fields
- id - order id number (required)
- domain - object which this order affects (required)
- type - type of operation to be performed (eg. ModifyNS_Domain) (required)
- status - status of this order (required)
- errorcode - if order could not be processed, contains specific subreg errorcode
- lastupdate - date of latest status modification
- message - additional human-readable status message
- payed - information if the order is already payed
- amount - the price of the order
Example
<?xml version="1.0" encoding="UTF-8" standalone="no"?> <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> <command> <info> <order:info xmlns:order="http://www.subreg.cz/epp/order-1.0"> <order:id>856274</order:id> </order:info> </info> <clTRID>SUBREG20120218T020501Z217</clTRID> </command> </epp>
<?xml version="1.0" encoding="UTF-8" standalone="no"?> <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> <response> <result code="1000"> <msg lang="en">Command completed successfully</msg> </result> <resData> <order:infData xmlns:order="http://www.subreg.cz/epp/order-1.0"> <order:id>856274</order:id> <order:domain>yourdomain.cz</order:domain> <order:type>Modify_Domain</order:type> <order:status>Pending_Authorization</order:status> <order:lastupdate>2012-02-18T02:02:03.0Z</order:lastupdate> <order:message>jdoe@example.com</order:message> <order:payed>1</order:payed> <order:amount>0.00</order:amount> </order:infData> </resData> <trID> <clTRID>SUBREG20120218T020501Z217</clTRID> <svTRID>SUBREG20120218T020501Z315</svTRID> </trID> </response> </epp>
Subreg EPP server documentation - version 1.0
|