Response Samples

A positive response that returns the traffic spent by the specified domains can look as shown below. This packet returns the information about traffic for two dates for two domains.

<packet version="1.4.1.2">

<domain>

<get_traffic>

   <result>

      <status>ok</status>

      <id>1234</id>

      <traffic>

          <date>2005-12-12</date>

          <http_in>4371212365846</http_in>

          <http_out>1234111122</http_out>

          <ftp_in>4121253</ftp_in>

          <ftp_out>163553</ftp_out>

          <smtp_in>123535</smpt_in>

          <smtp_out>341156</smtp_out>

          <pop3_imap_in>1545682</pop3_imap_in>

          <pop3_imap_out>15434674</pop3_imap_out>

      </traffic>

      <traffic>

          <date>2005-12-13</date>

          <http_in>4371978643846</http_in>

          <http_out>1234548722</http_out>

          <ftp_in>4121153</ftp_in>

          <ftp_out>123653</ftp_out>

          <smtp_in>123535</smpt_in>

          <smtp_out>341356</smtp_out>

          <pop3_imap_in>1511112</pop3_imap_in>

          <pop3_imap_out>16458674</pop3_imap_out>

      </traffic>

   </result>

   <result>

      <status>ok</status>

      <id>1247</id>

      <traffic>

          <date>2005-12-12</date>

          <http_in>4371243251846</http_in>

          <http_out>1234111122</http_out>

          <ftp_in>4125453</ftp_in>

          <ftp_out>123153</ftp_out>

          <smtp_in>123535</smpt_in>

          <smtp_out>341356</smtp_out>

          <pop3_imap_in>1543512</pop3_imap_in>

          <pop3_imap_out>15436374</pop3_imap_out>

      </traffic>

      <traffic>

          <date>2005-12-13</date>

          <http_in>4371243251846</http_in>

          <http_out>1234111122</http_out>

          <ftp_in>4125453</ftp_in>

          <ftp_out>123153</ftp_out>

          <smtp_in>123535</smpt_in>

          <smtp_out>341356</smtp_out>

          <pop3_imap_in>1543512</pop3_imap_in>

          <pop3_imap_out>15436374</pop3_imap_out>

      </traffic>

   </result>

</get_traffic>

</domain>

</packet>

<packet version="1.4.2.0">

<domain>

<get_traffic>

   <result>

      <status>ok</status>

      <filter-id>1234</filter-id>

      <id>1234</id>

      <traffic>

          <date>2005-12-12</date>

          <http_in>4371212365846</http_in>

          <http_out>1234111122</http_out>

          <ftp_in>4121253</ftp_in>

          <ftp_out>163553</ftp_out>

          <smtp_in>123535</smpt_in>

          <smtp_out>341156</smtp_out>

          <pop3_imap_in>1545682</pop3_imap_in>

          <pop3_imap_out>15434674</pop3_imap_out>

      </traffic>

      <traffic>

          <date>2005-12-13</date>

          <http_in>4371978643846</http_in>

          <http_out>1234548722</http_out>

          <ftp_in>4121153</ftp_in>

          <ftp_out>123653</ftp_out>

          <smtp_in>123535</smpt_in>

          <smtp_out>341356</smtp_out>

          <pop3_imap_in>1511112</pop3_imap_in>

          <pop3_imap_out>16458674</pop3_imap_out>

      </traffic>

   </result>

   <result>

      <status>ok</status>

      <filter-id>1247</filter-id>

      <id>1247</id>

      <traffic>

          <date>2005-12-12</date>

          <http_in>4371243251846</http_in>

          <http_out>1234111122</http_out>

          <ftp_in>4125453</ftp_in>

          <ftp_out>123153</ftp_out>

          <smtp_in>123535</smpt_in>

          <smtp_out>341356</smtp_out>

          <pop3_imap_in>1543512</pop3_imap_in>

          <pop3_imap_out>15436374</pop3_imap_out>

      </traffic>

      <traffic>

          <date>2005-12-13</date>

          <http_in>4371243251846</http_in>

          <http_out>1234111122</http_out>

          <ftp_in>4125453</ftp_in>

          <ftp_out>123153</ftp_out>

          <smtp_in>123535</smpt_in>

          <smtp_out>341356</smtp_out>

          <pop3_imap_in>1543512</pop3_imap_in>

          <pop3_imap_out>15436374</pop3_imap_out>

      </traffic>

   </result>

</get_traffic>

</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.

If the operation fails, a negative response can look as follows:

<packet version="1.4.1.2">

<domain>

<get_traffic>

   <result>

      <status>error</status>

      <errcode>1023</errcode>

      <errtext>Operation failed.</errtext>

      <id>1324</id>

   </result>

   <result>

      <status>error</status>

      <errcode>1023</errcode>

      <errtext>Operation failed.</errtext>

      <id>1247</id>

   </result>

</get_traffic>

</domain>

</packet>

<packet version="1.4.2.0">

<domain>

<get_traffic>

   <result>

      <status>error</status>

      <errcode>1023</errcode>

      <errtext>Operation failed.</errtext>

      <filter-id>1234</filter-id>

      <id>1324</id>

   </result>

   <result>

      <status>error</status>

      <errcode>1023</errcode>

      <errtext>Operation failed.</errtext>

      <filter-id>1247</filter-id>

      <id>1247</id>

   </result>

</get_traffic>

</domain>

</packet>

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.