Webhooks push events instead of polling
Because the call comes from outside, delivery becomes at-least-once, so a receiver must tolerate retries and prove the origin rather than assume it is safe. One event, one callback A webhook turns the usual direction of an API call around: instead of a client polling for fresh data, the provider sends an HTTP request to a URL you registered whenever an event happens. The payload is a small, self-contained description of what changed, delivered straight to an endpoint that is often on an entirely different server. Because the publisher initiates the call, the subscriber stops reopening connections and simply waits for something to arrive, which is how delivery can feel nearly instant without continuous polling. ...