<?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 Re: SASE Public API v3.0 in SASE and Remote Access</title>
    <link>https://community.checkpoint.com/t5/SASE-and-Remote-Access/SASE-Public-API-v3-0/m-p/281390#M14619</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.checkpoint.com/t5/user/viewprofilepage/user-id/7"&gt;@PhoneBoy&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;any idea to add also client status?&lt;/P&gt;&lt;P&gt;I mean users connected\authenticated?&lt;/P&gt;&lt;P&gt;This will be very useful to avoid each time to logon on the portal &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;</description>
    <pubDate>Mon, 24 Aug 2026 07:59:08 GMT</pubDate>
    <dc:creator>Giammarco</dc:creator>
    <dc:date>2026-08-24T07:59:08Z</dc:date>
    <item>
      <title>SASE Public API v3.0</title>
      <link>https://community.checkpoint.com/t5/SASE-and-Remote-Access/SASE-Public-API-v3-0/m-p/279988#M14609</link>
      <description>&lt;P&gt;We've merged the Public API into a single, unified spec — no more hopping between the old Harmony SASE docs and SwaggerHub. Everything's in one place now: &lt;A id="menur942" class="fui-Link ___1q1shib f2hkw1w f3rmtva f1ewtqcl fyind8e f1k6fduh f1w7gpdv fk6fouc fjoy568 figsok6 f1s184ao f1mk8lai fnbmjn9 f1o700av f13mvf36 f1cmlufx f9n3di6 f1ids18y f1tx3yz7 f1deo86v f1eh06m1 f1iescvh fhgqx19 f1olyrje f1p93eir f1nev41a f1h8hb77 f1lqvz6u f10aw75t fsle3fq f17ae5zn" title="https://app.swaggerhub.com/apis/check-point/sase-api" href="https://app.swaggerhub.com/apis/Check-Point/SASE-API" rel="noreferrer noopener" aria-label="Link https://app.swaggerhub.com/apis/Check-Point/SASE-API" target="_blank"&gt;&lt;STRONG&gt;https://app.swaggerhub.com/apis/Check-Point/SASE-API&lt;/STRONG&gt;&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Already there (now just consolidated into v3):&lt;/STRONG&gt; full network lifecycle management for Standard and Enhanced networks, gateway instances, regions, route tables, and tunnels (Wireguard, OpenVPN, IPSec single &amp;amp; redundant), address and service objects, application management, and firewall policy — all the CRUD you'd expect from prior versions, just under one spec now instead of split across old docs pages.&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;What's new in v3:&lt;/STRONG&gt;&lt;BR /&gt;• &lt;STRONG&gt;Internet Access Policies&lt;/STRONG&gt; — SWG access-policy rules and HTTPS Inspection rules&lt;BR /&gt;• &lt;STRONG&gt;Web Category&lt;/STRONG&gt; and &lt;STRONG&gt;Application Control&lt;/STRONG&gt; object catalogs, plus an &lt;STRONG&gt;Updatable Objects&lt;/STRONG&gt; feed&lt;BR /&gt;• &lt;STRONG&gt;Private DNS&lt;/STRONG&gt; management for Standard and Enhanced networks, at both network and region level&lt;BR /&gt;• &lt;STRONG&gt;Split Tunneling&lt;/STRONG&gt; configuration API&lt;BR /&gt;• &lt;STRONG&gt;Settings&lt;/STRONG&gt; — our first account-level surface in the public API (support-options for now, more to come)&lt;BR /&gt;• &lt;STRONG&gt;Granular per-rule firewall logging&lt;/STRONG&gt; — the firewall-policy endpoint now supports a &lt;CODE&gt;logEnabled&lt;/CODE&gt; flag per rule, not just at the policy level&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;LI-WRAPPER&gt;&lt;/LI-WRAPPER&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 21 Jul 2026 15:01:22 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/SASE-and-Remote-Access/SASE-Public-API-v3-0/m-p/279988#M14609</guid>
      <dc:creator>PhoneBoy</dc:creator>
      <dc:date>2026-07-21T15:01:22Z</dc:date>
    </item>
    <item>
      <title>Re: SASE Public API v3.0</title>
      <link>https://community.checkpoint.com/t5/SASE-and-Remote-Access/SASE-Public-API-v3-0/m-p/281390#M14619</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.checkpoint.com/t5/user/viewprofilepage/user-id/7"&gt;@PhoneBoy&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;any idea to add also client status?&lt;/P&gt;&lt;P&gt;I mean users connected\authenticated?&lt;/P&gt;&lt;P&gt;This will be very useful to avoid each time to logon on the portal &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Mon, 24 Aug 2026 07:59:08 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/SASE-and-Remote-Access/SASE-Public-API-v3-0/m-p/281390#M14619</guid>
      <dc:creator>Giammarco</dc:creator>
      <dc:date>2026-08-24T07:59:08Z</dc:date>
    </item>
    <item>
      <title>Re: SASE Public API v3.0</title>
      <link>https://community.checkpoint.com/t5/SASE-and-Remote-Access/SASE-Public-API-v3-0/m-p/281492#M14625</link>
      <description>&lt;P&gt;Perusing the API in general, it seems more geared toward configuration versus monitoring.&lt;BR /&gt;Not sure it's in the plan.&lt;/P&gt;</description>
      <pubDate>Tue, 25 Aug 2026 16:17:12 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/SASE-and-Remote-Access/SASE-Public-API-v3-0/m-p/281492#M14625</guid>
      <dc:creator>PhoneBoy</dc:creator>
      <dc:date>2026-08-25T16:17:12Z</dc:date>
    </item>
  </channel>
</rss>

