What Is a Webhook? Understanding It With a Restaurant Waiting Ticket

TL;DR: A webhook is an agreement that, when something happens, a signal is sent automatically to a pre-set address. It works exactly like a waiting ticket at a snack shop. Instead of repeatedly asking whether a table is free, you take a ticket, and when a table opens, the shop reaches out first. This article ties that structure to one analogy and ends with you receiving a real signal directly through webhook.site.

When you hand automation work to an AI, you sometimes get the answer “register this URL as a webhook.” In an earlier article, What Is an API?, I explained APIs using a snack-shop order slip. Webhooks work differently. You don’t send a request first, like with an order slip. Instead, the other side reaches out to you when something happens, even if you do nothing. The setting is still the same snack shop, but this time it’s the line outside the store, before you get a seat. You can follow this article without having read the earlier one.

This article is for anyone who is new to AI automation tools and stopped at the sentence “register a webhook.” By the end, you’ll understand why webhooks exist and will have received a real webhook signal yourself using webhook.site, a free service.

Contents

1. Instead of checking every 10 minutes, you take a ticket
2. Asking over and over is polling
3. Translating waiting terms into computer terms
4. Who sends the signal depends on the situation
5. Try it: receive a signal with webhook.site
6. If you want to read further

1. Instead of checking every 10 minutes, you take a ticket

Imagine you’re waiting outside a snack shop. If there are no free tables, you have two options. One is to go to the counter every few minutes and ask, “Is there a table free yet?” The other is to take a ticket, wait, and get a text when a table opens.

The first method is polling. The second is a webhook. Programs work the same way. You can build a program that repeatedly asks, “Is there a new order?” Or you can register an address once and only receive a signal at that address when an order actually comes in. When an AI says “register a webhook,” it means the second approach.

2. Asking over and over is polling

What would happen without webhooks? A program would have no choice but to keep asking, “Is there new data?” every few seconds or minutes. This repeated asking has a name: polling. Checking the counter every 10 minutes to see if a table is free is polling. Taking a ticket and waiting for a text is a webhook.

Placing the two methods side by side makes the difference clear. On the left is polling, where the customer has to keep moving. On the right is a webhook, where the shop moves first.

3. Translating waiting terms into computer terms

You don’t need to memorize the words on the right. If you meet the sentence “the webhook listens” in an automation explanation an AI wrote for you, read it by swapping in the left column. It means “a ticket is hung up and waiting.”

4. Who sends the signal depends on the situation

One thing needs clarifying here. All the examples so far have run in one direction: you take the ticket, and the other side sends the signal to you. But webhooks aren’t fixed in one direction. The reverse case, where the other side gives you an address, you register it, and you send signals to that address, is also called a webhook.

For example, Discord creates an address for each channel. If you register that address in your automation, your side can send results to it whenever a job finishes, and a post appears in the Discord channel. This time you’re not the customer taking the ticket; you’re playing the role of the shop that issues the ticket. How to create one on the actual screen is covered in Creating a Webhook in Discord.

5. Try it: receive a signal with webhook.site

You’ll quickly feel that you don’t need a special tool to receive a webhook once you try it yourself. All you need is a browser, and no sign-up is required.

1. Open https://webhook.site in your browser.
2. As soon as you arrive, a unique address that is hard to guess is generated automatically. At the top of the screen you’ll see a long address starting with https://webhook.site/. However, this address is not protected by a login, so anyone who knows it can view the records inside. This address is your ticket.
3. Copy that address, paste it into a new tab, and go there. That visit itself is one request sent to that address.
4. Go back to the original tab (the webhook.site screen), and the request you just sent appears immediately in the list on the left.

On a real service, much more varied content arrives at this kind of address. For example, an order system might send data in a form like the one below (this is an example, not something I actually received).

{"event":"new_order","item":"떡볶이","price":4000}

What you’ll check yourself is simpler than this. Because the visit to the address is itself the signal, only the visit record is saved, with no extra content. Below is the result I got when I actually followed these steps.

The free address has two limits. It is automatically deleted along with its data after seven days, and before that it records at most 100 entries. If your address disappears during practice or stops recording, go to webhook.site again and get a new address.

6. If you want to read further

This article focused on building the framework with an analogy. Once that framework is in place, the two resources below are good for filling in the details. Both are in Korean and free.

• Toss Payments Developer Center, “Webhook” (Toss Payments is a major South Korean payment provider.) It summarizes the webhook concept and the difference from polling, and links to a separate document for the registration steps.
• BizSpring, “Understanding Webhooks” (BizSpring is a South Korean tech blog.) It uses real-life examples such as payment completion, issue creation, and delivery tracking, and summarizes the difference from polling in a table.

The seven-day retention period and 100-record limit for free webhook.site addresses were confirmed in the official FAQ on August 31, 2026. Free plan terms can change on the service’s side, so if the screen shows different information, follow what the screen says.