<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic API. Filtering results in API / CLI Discussion</title>
    <link>https://community.checkpoint.com/t5/API-CLI-Discussion/API-Filtering-results/m-p/151127#M6884</link>
    <description>&lt;P&gt;Hello!&lt;BR /&gt;&lt;BR /&gt;Is there any way to return only the required fields from api requests? For example, I need to get all the rules by the "uuid" and "hitcount" fields, or just the hostnames. We need something similar to what fortigate's "fields" method does.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="fields.png" style="width: 999px;"&gt;&lt;img src="https://community.checkpoint.com/t5/image/serverpage/image-id/16971i433048838F1023BB/image-size/large?v=v2&amp;amp;px=999" role="button" title="fields.png" alt="fields.png" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 17 Jun 2022 08:26:17 GMT</pubDate>
    <dc:creator>Dmitriy2</dc:creator>
    <dc:date>2022-06-17T08:26:17Z</dc:date>
    <item>
      <title>API. Filtering results</title>
      <link>https://community.checkpoint.com/t5/API-CLI-Discussion/API-Filtering-results/m-p/151127#M6884</link>
      <description>&lt;P&gt;Hello!&lt;BR /&gt;&lt;BR /&gt;Is there any way to return only the required fields from api requests? For example, I need to get all the rules by the "uuid" and "hitcount" fields, or just the hostnames. We need something similar to what fortigate's "fields" method does.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="fields.png" style="width: 999px;"&gt;&lt;img src="https://community.checkpoint.com/t5/image/serverpage/image-id/16971i433048838F1023BB/image-size/large?v=v2&amp;amp;px=999" role="button" title="fields.png" alt="fields.png" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 17 Jun 2022 08:26:17 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/API-CLI-Discussion/API-Filtering-results/m-p/151127#M6884</guid>
      <dc:creator>Dmitriy2</dc:creator>
      <dc:date>2022-06-17T08:26:17Z</dc:date>
    </item>
    <item>
      <title>Re: API. Filtering results</title>
      <link>https://community.checkpoint.com/t5/API-CLI-Discussion/API-Filtering-results/m-p/151139#M6887</link>
      <description>&lt;P&gt;With Check Point's API, you have three "details-level" options: uid, standard, and full. Beyond that, filtering the data is the responsibility of the client application.&lt;/P&gt;
&lt;P&gt;Tat said, there isn't a lot of benefit to limiting the fields the server returns. Showing a single object with details-level uid takes about 60% of the time of showing 500 objects with full details. If you're in an extremely traffic-constrained environment, enabling compression is a much easier way to limit the data transferred.&lt;/P&gt;</description>
      <pubDate>Fri, 17 Jun 2022 13:48:20 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/API-CLI-Discussion/API-Filtering-results/m-p/151139#M6887</guid>
      <dc:creator>Bob_Zimmerman</dc:creator>
      <dc:date>2022-06-17T13:48:20Z</dc:date>
    </item>
  </channel>
</rss>

