API Filtering

• Using PI3.0, want to work API Filtering on Attribute "dateValue" of Reports "Client Sessions".
  Looking to get the Respons exceptet for Values of Attribute "Packets Sent" and "Packets Received" are "0". 
• API Resource: GET a Report
  Report: Client Sessions
  Customize: Client IP Address/Client MAC Address/AP name/SSID/Associated Time/DisAssociated Time/RSSI/Packets Sent/Packets Received
  Target: dateValue of Packets Sent and Packets Received
  Filtering: not equals "0" or greater than "0"
  Example:
            <entry>
              <attributeName>lradName</attributeName>
              <dataValue>xxxx</dataValue>
              <displayName>AP Name</displayName>
            </entry>
            <entry>
              <attributeName>sessionStartTime</attributeName>
              <dataValue>Tue Mar 08 12:14:24 JST 2016</dataValue>
              <displayName>Association Time</displayName>
            </entry>
            <entry>
              <attributeName>sessionEndTime</attributeName>
              <dataValue>Tue Mar 08 12:19:20 JST 2016</dataValue>
              <displayName>Disassociation Time</displayName>
            </entry>
            <entry>
              <attributeName>packetsSent</attributeName>
              <dataValue>0</dataValue>                      ←Target
              <displayName>Packets Sent</displayName>
            </entry>
            <entry>
              <attributeName>packetsReceived</attributeName>
              <dataValue>0</dataValue>                      ←Target
              <displayName>Packets Received</displayName>
            </entry> 

Tried API requests following, Failure.
/webacs/api/v1/op/reportService/getReport?reportTitle= xx&attributeName=”packetsSent”&dataValue=ne("0")
/webacs/api/v1/op/reportService/getReport?reportTitle= xx&and.filter=true&attributeName=”packetsSent”&dataValue=ne("0") 

Would you tell us for the correct URL

Unfortunately, none of the report resources support filtering, as noted in the "Resource Information" infobox. 

Have you tried looking into the Client Sessions resource instead.