Retrieving info on a secret key
This request packet retrieves info on secret key 6575fae36288be6d1bad40b99808e37f.
<packet version="1.4.2.0">
<secret_key>
<get_info>
<filter>
<key>6575fae36288be6d1bad40b99808e37f</key>
</filter>
</get_info>
</secret_key>
</packet>
If the key was found on the server, a response can look as follows:
<packet version="1.4.2.0">
<secret_key>
<get_info>
<result>
<status>ok</status>
<key_info>
<key>6575fae36288be6d1bad40b99808e37f</key>
<ip_address>192.0.2.1</ip_address>
<description></description>
</key_info>
</result>
</get_info>
</secret_key>
</packet>
If the key was not found on the server, the response looks as follows:
<packet version="1.4.2.0">
<secret_key>
<get_info>
<result>
<status>error</status>
<errcode>1013</errcode>
<errtext>Key is not found</errtext>
<key>6575fae36288be6d1bad40b99808e37f</key>
</result>
</get_info>
</secret_key>
</packet>
Retrieving info on multiple secret keys
This request packet retrieves info on secret keys 6575def8 and 6576d1ef7.
<packet version="1.4.2.0">
<secret_key>
<get_info>
<filter>
<key>6575def8</key>
<key>6576d1ef7</key>
</filter>
</get_info>
</secret_key>
</packet>
A possible response from the server can look as follows:
<packet version="1.4.2.0">
<secret_key>
<get_info>
<result>
<status>ok</status>
<key_info>
<key>6575def8</key>
<ip_address>192.0.2.1</ip_address>
<description>For User3</description>
</key_info>
</result>
<result>
<status>ok</status>
<key_info>
<key>6576d1ef7</key>
<ip_address>192.0.2.2</ip_address>
<description></description>
</key_info>
</result>
</get_info>
</secret_key>
</packet>