A webhook is a technology that enables real-time communication between systems. It works by sending automated messages or data to a specified URL when certain events occur. Unlike traditional APIs, which require constant polling for updates, webhooks push information immediately as the event happens, making them efficient for triggering actions or updating systems in real time.
Within the WISMOlabs platform, every process, such as order shipment or return, is driven by a series of events. For example, an outbound shipment may progress through stages like packaging, pickup by the carrier, shipping, out for delivery, and final delivery. Other events might include customs clearances for international deliveries, delays, failed delivery attempts, or a return to sender. Similarly, a return process could involve return request initiation, return request approval, shipment back to the return processing center, verification, and refund issuance. Each of these steps is an event that can trigger a webhook notification.
Webhook notifications are vital for keeping your entire technological stack in sync, ensuring all systems are updated with the latest status changes. WISMOlabs offers fully configurable webhook payloads that can be customized using the Liquid templating language. All webhook payloads must be valid JSON format. Please ensure compatibility with your systems.
This flexibility allows retailers to ensure all aspects of their order and return processes are aligned and responsive to customer needs in real time.
Because webhooks operate via simple HTTP POST requests from unknown sources, malicious actors can exploit this mechanism to send unauthorized data. This vulnerability can lead to data breaches, unauthorized actions, or other security incidents within your application.
Note: It is extremely important to ensure that the rendered Liquid template results in valid JSON format. When using Liquid variables that may have no or null values, use the default filter to maintain JSON consistency. This ensures the value is wrapped in brackets and the JSON remains valid. For example, when handling optional values, use:
"parameter": {{payload.optional.OPTIONAL_VALUE | default: ''}}If your configured endpoint fails to retrieve a webhook payload due to unavailability and does not respond with a 200 OK message, WISMOlabs will retry using an exponential backoff schedule:
This gives you time to fix a potentially broken endpoint without bottlenecking the system with failing messages.