<?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 Using feature service webhooks or feature server change APIs? in ArcGIS Enterprise Questions</title>
    <link>https://community.esri.com/t5/arcgis-enterprise-questions/using-feature-service-webhooks-or-feature-server/m-p/1565207#M41153</link>
    <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;We use ArcGIS Enterprise as a system of record for asset data and want to update data to another secondary system that needs this data too in a near real time way (must have &amp;lt;1 hour, and preferably &amp;lt;5 min). We are thinking of using feature service webhooks (insert/update/delete event triggers) or feature server change API to fetch inserts/updates/deletes every few minutes.&lt;/P&gt;&lt;P&gt;What are the (dis)advantages of using feature service webhooks over feature server change APIs?&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Advantage feature service webhooks over feature server change APIs:&lt;/P&gt;&lt;P&gt;- Feature service webhooks triggers event instantly&lt;/P&gt;&lt;P&gt;- If using a webhook, the trigger endpoint for sending creates/updates/deletes from ArcGIS can also be triggered without ArcGIS (e.g. ArcGIS can be compared to secondary system on a weekly schedule, and then creates/updates/deletes can still be sent to trigger endpoint to get eventual consistency in case of errors. This is not easy via polling API to check for changes.)&lt;/P&gt;&lt;P&gt;- ...?&lt;/P&gt;&lt;P&gt;Advantages feature server change APIs over feature service webhooks:&lt;/P&gt;&lt;P&gt;- Very stable&lt;/P&gt;&lt;P&gt;- Fetching feature server changes via API gives more options to filter out specific inserts/updates/deletes&lt;/P&gt;&lt;P&gt;- ...?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 13 Jan 2025 12:10:35 GMT</pubDate>
    <dc:creator>DavidLovesArcGIS</dc:creator>
    <dc:date>2025-01-13T12:10:35Z</dc:date>
    <item>
      <title>Using feature service webhooks or feature server change APIs?</title>
      <link>https://community.esri.com/t5/arcgis-enterprise-questions/using-feature-service-webhooks-or-feature-server/m-p/1565207#M41153</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;We use ArcGIS Enterprise as a system of record for asset data and want to update data to another secondary system that needs this data too in a near real time way (must have &amp;lt;1 hour, and preferably &amp;lt;5 min). We are thinking of using feature service webhooks (insert/update/delete event triggers) or feature server change API to fetch inserts/updates/deletes every few minutes.&lt;/P&gt;&lt;P&gt;What are the (dis)advantages of using feature service webhooks over feature server change APIs?&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Advantage feature service webhooks over feature server change APIs:&lt;/P&gt;&lt;P&gt;- Feature service webhooks triggers event instantly&lt;/P&gt;&lt;P&gt;- If using a webhook, the trigger endpoint for sending creates/updates/deletes from ArcGIS can also be triggered without ArcGIS (e.g. ArcGIS can be compared to secondary system on a weekly schedule, and then creates/updates/deletes can still be sent to trigger endpoint to get eventual consistency in case of errors. This is not easy via polling API to check for changes.)&lt;/P&gt;&lt;P&gt;- ...?&lt;/P&gt;&lt;P&gt;Advantages feature server change APIs over feature service webhooks:&lt;/P&gt;&lt;P&gt;- Very stable&lt;/P&gt;&lt;P&gt;- Fetching feature server changes via API gives more options to filter out specific inserts/updates/deletes&lt;/P&gt;&lt;P&gt;- ...?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 13 Jan 2025 12:10:35 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-enterprise-questions/using-feature-service-webhooks-or-feature-server/m-p/1565207#M41153</guid>
      <dc:creator>DavidLovesArcGIS</dc:creator>
      <dc:date>2025-01-13T12:10:35Z</dc:date>
    </item>
  </channel>
</rss>

