Webhook
A Webhook is a mechanism by which one system automatically sends (“pushes”) a real-time notification to another system when a specific event occurs, by making an HTTP call to a URL the receiving system has registered. It is often described as a “reverse API”: instead of a system repeatedly asking (polling) “has anything changed?”, the source system notifies it the moment something does.
Webhooks are ideal for event-driven, real-time updates in logistics: a carrier or tracking platform can fire a webhook to a freight or ERP system the instant a container is gated in, loaded, discharged, or its status changes, so the receiving system updates immediately without constant polling. This makes integrations more efficient and more timely than repeatedly calling an API. Webhooks complement APIs (which the receiver uses to pull data on demand) with a push model for notifications. They are increasingly used for shipment milestone events, tracking and status updates, and are a key building block of real-time supply-chain visibility and system integration. Understanding webhooks is useful for building responsive, event-driven connections between logistics systems.
Constantly polling an API to ask “anything new?” is wasteful and slow — a webhook flips it, pushing the update the instant a container is gated, loaded or its status changes. That event-driven model makes integrations timelier and lighter, which is why webhooks are central to real-time shipment visibility. They are a key building block for responsive connections between logistics systems.
How is a webhook different from an API call?
With an API the receiver pulls data on demand; a webhook pushes a notification automatically when an event occurs, avoiding constant polling.
What are webhooks used for in logistics?
Real-time event notifications such as container gate-in, load, discharge and status changes, so systems update the moment something happens.