A webhook is an automated message sent from an app when something happens. It is a callback function that allows event-driven communication between 2 application programming interfaces (APIs). Webhooks have a payload and are sent to a unique URL, essentially the app’s phone number or address. They are always faster than polling and require only a little input.
Webhook is just like SMS notifications; for example, your bank sends you an SMS when you make a transfer, or an online store sends you an order confirmation message. They already have your phone number or email address, so the app or website knows where to send messages whenever an event occurs.
When you use a webhook for an e-commerce store, you need to tell the originating app where to send the message (the webhook URL of the receiving app). Let’s say someone makes a purchase in your online store and checks out. An event has occurred, so you will get a message about the order, and the customer will get a message about their order confirmation, all using a webhook.
Many apps use webhooks to receive small amounts of data from other apps. They can also trigger an automation workflow in certain apps.
How Does Webhook Work
Webhook communication sends an HTTP request from a source application to a destination application. If an event takes place in the source application, the HTTP request containing data relating to the triggered event is sent to the destination application’s endpoint. The endpoint is sometimes called the webhook URL; it is the contact information submitted by the destination application to the source application for receiving webhook requests.
These webhook requests can be sent using the GET or POST request methods. It depends on the webhook provider’s preferences. After the source application sends the request, the destination application processes it, and the user can be notified of the events that have taken place.