A server-to-server callback that pushes data to a URL you register when an event fires - push delivery without a held-open connection.
A webhook is an HTTP callback: instead of a client polling for changes, the provider sends an HTTP request to a URL the consumer registered whenever a relevant event occurs. It is a lightweight way to get push delivery without maintaining a persistent streaming connection, well suited to lower-frequency events like a completed backfill or a threshold being crossed.
The reliability details are what separate a toy webhook from a production one. Deliveries can fail, so the sender needs retries with backoff, and the receiver needs to be idempotent so a retried event is not processed twice. Signing each payload lets the receiver verify it genuinely came from the provider. Get those right and webhooks are a clean complement to a streaming API for event-driven consumers.
A live evaluation measures EdgeOrigin against your coverage requirements: decision-ready real-time data, delivery latency into your systems, and record-level provenance.