Webhook
Definition
A webhook automatically informs another system about an occurred event.
An event-driven HTTP call with which one system informs another about an event.
Simply explained
When something happens, a system immediately sends a message to another—e.g., after paying an order.
Why it matters in practice
The term contributes to secure, maintainable, and high-performance web applications as well as resilient technical decisions.
Example from business
A shop system reports paid orders to the merchandise management system; the recipient processes event IDs idempotently.
Limits and pitfalls
- Delivery is often at least once; signature, replay protection, retries, order, and timeout must be regulated.
Origin & history
Webhooks became widespread with SaaS APIs as a simple alternative to regular polling.
Use in mid-sized companies
- Possible application: A shop system reports paid orders to the merchandise management system; the recipient processes event IDs idempotently.
Frequently asked questions
What does webhook mean?
An event-driven HTTP call with which one system informs another about an event. What should be considered? Delivery is often at least once; signature, replay protection, retries, order, and timeout must be regulated.
Sources
- Webhooks documentation · GitHub, Webhooks documentation
Source checked on 10.10.2026. Editorial usage examples are hypothetical; no evidence of real customer results.
Editorially reviewed on: