<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Events on API Course</title>
    <link>https://apicourse.com/tags/events/</link>
    <description>Recent content in Events on API Course</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 02 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://apicourse.com/tags/events/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Webhooks vs Polling: When to Push, When to Pull</title>
      <link>https://apicourse.com/webhooks-vs-polling-when-to-push-when-to-pull/</link>
      <pubDate>Sat, 02 May 2026 00:00:00 +0000</pubDate>
      <guid>https://apicourse.com/webhooks-vs-polling-when-to-push-when-to-pull/</guid>
      <description>&lt;p&gt;Every integration eventually confronts the same question: how does my system learn that something changed in someone else&amp;rsquo;s system? The two answers are polling and webhooks. Polling asks the question repeatedly. Webhooks get notified when the answer changes. Understanding which approach fits a given situation — and why — shapes everything from latency and cost to reliability and operational complexity.&lt;/p&gt;&#xA;&lt;h2 id=&#34;polling-the-default-that-mostly-works&#34;&gt;Polling: The Default That Mostly Works&lt;/h2&gt;&#xA;&lt;p&gt;Polling is the simpler mental model. Your application sends requests to an API on a schedule — every 30 seconds, every minute, every hour — and checks whether anything has changed since the last check. If yes, process the changes. If no, wait for the next interval.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
