An automatic message one system sends to another when a specific event happens, such as a completed payment or new form submission. Unlike repeated checking, a webhook pushes the update when it occurs and should be authenticated and tested.
How Webhook Works
A webhook sends data automatically from one system to another when a defined event occurs. Instead of the receiving system repeatedly asking whether something changed, the sending system pushes an event message to a specified URL.
Simple Example
A payment service sends a webhook to the site when a payment succeeds so membership access can be activated.
Why It Matters for Beginners
This matters because webhooks allow near-real-time automation between services. Failed or unsecured webhooks can cause missed payments, incorrect account access, duplicate actions, or data exposure.
A Common Mistake
Accepting webhook requests without verification or failing to handle retries and duplicate events safely.
Related Terms
- API
- Automation
- Payment Gateway