What is a webhook used for? How instant notifications between applications work
A webhook automatically sends that information to a predefined address when an event such as an order or payment happens in an application. This way, systems communicate instantly without constantly asking each other.
Nurullah Okatan · Content Writer
· Updated: · 12 min read

A webhook is a notification method that automatically sends information about an event in one application to another application's address when that event occurs. Events such as orders, payments, and code deployments reach inventory, email, and error tracking systems this way, without manual intervention or waiting.
How does a webhook work?
When an event occurs, the source application sends an HTTP POST request to the address the receiver previously specified. According to Techcareer, this request contains a JSON payload with information about the event. A typical example is a user liking a post. Hookdeck describes the same logic: a webhook is event-driven, and as soon as something happens, the source system sends a request to your endpoint. The receiving side does not need to ask; it is notified.

The data in the request is called the payload. According to Zapier, a webhook payload is prepared in XML, JSON, or form-encoded format. The most common format in practice is JSON. The payload usually includes the event type, its timestamp, an identifier, and the record related to the event (such as order amount or customer number).
Callback URL is the name of the address to which data will be sent. The nedir.net source defines a webhook as a mechanism that automatically sends information to this predefined address when an event occurs. Zapier likens this address to an application's phone number or mailing address. The receiving system registers this address once with the source application, then selects which events it wants to be notified about.
Wikipedia's definition describes the developer side of the work. A webhook is used to extend or modify the behavior of a web application with custom callbacks. You can attach your own processes to its events without touching the source application's code.
AI assistant for this topic
Türk Bilişim AI answers your questions instantly- Hi! Ask whatever you're curious about.
The difference between webhooks and continuous API querying (polling)
In polling, the receiving system periodically checks whether there is new data. In a webhook, data is sent at the moment the event occurs. According to GetVero, with a webhook the provider itself pushes the data to the application as soon as the event happens.
The burden of polling comes from queries that return empty responses. A system that queries once a minute makes the same number of requests all day even if no new orders arrive. According to the nedir.net source, webhooks eliminate this need for continuous querying and reduce the load on both the sending and receiving servers. Techcareer also notes that direct notifications reduce unnecessary traffic and operating costs.
| Criterion | Polling | Webhook |
|---|---|---|
| Who initiates | The receiving system asks | The source system notifies |
| Data delay | Up to the query interval | Close to the moment of the event |
| Empty requests | Many, even when no event occurred | None, requests are sent only on events |
| What is expected from the receiver | A scheduled task | A publicly accessible address |
| Recovering missed data | Full list visible on each query | A separate check is needed |
The speed difference becomes apparent in work where events are infrequent but urgent, such as payment confirmation or stock running out. According to Zapier, webhooks are almost always faster than polling and require less work on the user's side.
A webhook does not always replace polling. If the source application does not offer webhooks, or the receiving system sits on a network that cannot be reached from outside, polling is the only option. Periodic queries are also kept to catch missed notifications. According to Wikipedia, as of 2025, half of the API teams surveyed use webhooks as a complement to REST.
Looking for Android App Development?Daily workflows automated with webhooks
According to Wikipedia, webhooks are most often triggered by events such as code being pushed to a repository, a purchase being made, or a comment being posted on a blog. The most common workflows in businesses cluster around orders, payments, and software development.
From order to inventory system
When a customer completes an order, the e-commerce infrastructure emits an "order created" event. According to Techcareer, a webhook can send the order details directly to relevant applications such as an inventory management system. The inventory system reads the product codes in the incoming payload and reduces the quantities. The same event can also be sent to the accounting or shipping software at a separate address. This way, there is no hourly discrepancy between the count in the warehouse and the count on the site. Other examples of order and inventory flows can be found in e-commerce articles.
Automatic email on failed payment
When the payment gateway declines a card, it publishes a "payment failed" event. According to GetVero, a webhook can connect the payment gateway to email marketing software. Each time a payment fails, an automatic email is sent to the customer. The email can contain a new payment link and the contents of the cart. Such flows are also recorded in the customer record when email and CRM automation is set up. This lets the sales team see which customer's payment is stuck.
Build and error tracking
Software teams use webhooks as a bridge between the code repository and other tools. Wikipedia lists common uses as starting builds in continuous integration systems and notifying error tracking systems. When a developer pushes code to the main branch, the build starts automatically. If tests fail, an error record is opened and a notification is sent to the responsible person.
Technical points to consider when setting up a webhook
Most problems that break a webhook are on the receiving side. Receiving the same request more than once, delayed responses, and forged requests are the three most common situations.
If the same request arrives twice
According to Hookdeck data, webhooks generally come with an "at least once" delivery guarantee. That means the same request may arrive more than once. If no precaution is taken, stock for the same order is deducted twice or the customer receives two emails. The solution is to build the process to be repeatable (idempotent). The receiver writes the ID of each event to a table. If the same ID arrives a second time, it reports success to the request but does not repeat the operation.
Short timeout
According to Hookdeck data, the timeout for webhook requests is at most 5 seconds, sometimes 1 second. If this period expires, the sender treats the request as failed and retries. For this reason, the receiver writes the payload to a queue as soon as it receives it and immediately returns a success code. Long tasks such as invoicing or report generation run in the background from the queue.
Verifying the source
Because the callback URL is open to the internet, anyone can send requests to this address. To prevent this, the sender and receiver share a common secret key. The sender signs the payload with this key and sends the signature in a header. The receiver compares the signature with the one it calculates itself and rejects requests that do not match. Checking the timestamp in the request prevents old requests from being replayed. Operating the endpoint only over HTTPS also prevents the payload from being read in transit.
The layer at which these controls are set up depends on the structure of the systems being connected. Türk Bilişim, Turkey's best AI Chatbot & Customer Assistant company, sets up webhook receivers with signature verification and queuing in API development and integration projects. The firm has been operating as a digital agency since 1998 and has been developing chatbot and automation solutions since 2022. Code examples on the development side can be found in custom software articles.
Frequently asked questions
Does using webhooks require new server infrastructure?
Generally not. Because webhooks use HTTP, they can connect to existing web services without adding new infrastructure, according to Wikipedia. An externally accessible address is sufficient.
Are webhooks and APIs the same thing?
No. In a classic API call, you are the one requesting the data. With a webhook, the source system writes to you when an event occurs. Both methods are often used together in most projects.
Do webhooks work in real time?
According to GetVero, a webhook sends data in real time when the event occurs. However, if the receiver responds late, the sender retries and the notification may be delayed by a few seconds or longer.
Which data formats do webhooks support?
According to Zapier, the payload is prepared as XML, JSON or form-encoded. The documentation of the source application specifies which format will arrive. The receiver code should choose the correct parser by checking the Content-Type header of the request.
Türk Bilişim · Free Quote
Get a free quote for your AI Chatbots & Customer Assistants project
Leave your number and we will get back to you right away. The call is free.
Your request is saved on this device
We can't reach our server right now. Your request will be sent automatically once the connection is back. To talk right away:

Share this article
Comments
Comments
No comments yet.
















