Webhooks are an effective communication method for online applications that let you send requests to an arbitrary URL whenever certain events occur in a shop, e.g. an order is made, the basket is edited, a customer registers, etc. The target system will get notified automatically which eliminates the need for polling the shop API directly to find out about any changes. This feature is one of many we implemented as part of our Open System as a Service philosophy.
We enabled webhooks to be configured for the following events. The list will grow as we receive more ideas from interested developers:
If after being triggered a webhook does not receive a response from the target system, it will be triggered again up to 10 more times over a span of 3 days.
Communicating via the API usually means a store is continuously polled with requests from external applications which aim to detect whether certain events have taken place. This can lead to unnecessary loads on the server, especially if there are multiple instances of such integrations present in a single store. Trying to solve the issue by reducing the number of requests can in turn lead to synchronization issues on the target system, etc.
Webhooks are an obvious solution in such scenarios – target systems are instantly notified of certain events by 'push messages'. This completely removes the need to periodically poll shops with API requests and improves the overall integration performance.
Find out more information and check out some examples on: