Webhook
A webhook sends an event from one system to another when something changes. The receiver should verify authenticity and handle delayed or repeated delivery safely.
A worked example
A practical example to make the concept clear.
| Step | Illustrative record and result |
|---|---|
| Starting record | An example delivery system changes OUT-DEMO-11 to “dispatched” and sends event EVT-DEMO-11. |
| Change or calculation | The receiving service verifies the event and records that this delivery was dispatched. |
| Meaning and exception | If EVT-DEMO-11 arrives twice, a stored event reference prevents the same update or notification being applied twice. Delayed events also need an agreed ordering rule. |
Why it matters
An event can update the next team without waiting for a manual lookup. Agree which events matter, what their references mean and how repeated or late events are handled before connecting live systems.
Make it practical
How does the receiver verify and deduplicate a delayed callback? Test the answer with the exact release and application package under consideration. Explore Datrylo applications.