Response Samples

A positive response got from the server after updating the specified domains (e.g. with ID 2435 and ID 2446) looks as follows:

<packet version="1.4.1.2">

<domain>

<set>

   <result>

      <status>ok</status>

      <id>2435</id>

   </result>

   <result>

      <status>ok</status>

      <id>2446</id>

   </result>

</set>

</domain>

</packet>

<packet version="1.4.2.0">

<domain>

<set>

   <result>

      <status>ok</status>

      <filter-id>2435</filter-id>

      <id>2435</id>

   </result>

   <result>

      <status>ok</status>

      <filter-id>2446</filter-id>

      <id>2446</id>

   </result>

</set>

</domain>

</packet>

Notice the difference in these identical packets sent using different versions of API RPC:

• versions 1.4.1.2 and earlier return the domain identifier in its id node;
• versions 1.4.2.0 and later return the filtering parameter (the filter-id node) and the domain identifier (the id node). These two nodes can coincide if the domain was filtered by domain_id.

A negative response can look as follows:

<packet version="1.4.1.2">

<domain>

<set>

   <result>

      <status>ok</status>

      <id>2435</id>

   </result>

   <result>

      <status>error</status>

      <errcode>1013</errcode>

      <errtext>Object not found.</errtext>

   </result>

</set>

</domain>

</packet>

<packet version="1.4.2.0">

<domain>

<set>

   <result>

      <status>ok</status>

      <filter-id>2435</filter-id>

      <id>2435</id>

   </result>

   <result>

      <status>error</status>

      <errcode>1013</errcode>

      <errtext>Object not found.</errtext>

      <filter-id>2446</filter-id>

   </result>

</set>

</domain>

</packet>

The left packet is sent via API RPC 1.4.1.2 and does not return the domain identifier. The right packet is sent using API RPC 1.4.2.0, it indicates the filtering parameter (this time the domain ID) in the filter-id node.