You could ring the front desk every five minutes asking “Is my taxi here yet?” Or they could just call you when it arrives.
You’ve ordered a taxi at a hotel. You could keep ringing the front desk: “Is it here yet? How about now?” Or you could sit back and let the desk ring your room when the taxi pulls up.
A webhook is the desk ringing you. It’s a message one app sends to another automatically, the moment something happens. No need to keep asking.
Everyday examples
- a payment goes through and the shop's system is told straight away
- someone fills in a form and a message appears in your team chat
- a parcel is delivered and the online shop updates your order
Why it beats asking
Checking over and over (called polling) is slow and wasteful. A webhook means you hear the news instantly. You only hear from it when there’s news.
What it isn’t
It isn’t a hook you can see. It’s just a web address you give the other service: “When this happens, send a message here.”
Where the comparison breaks down
If you’re out when the desk rings, they’ll leave a note. If your app is down when a webhook arrives, the message can be lost, unless the sender tries again.
How the words fit together
With an API, you ask. With a webhook, you’re told. Webhooks are often the glue in an integration between two apps.
Webhooks are how many “when this happens, do that” automations work, like getting a message when someone pays you or fills in a form.

When you'll hear it
“Set up a webhook.” Tell the other service to send us a message automatically when something happens.
“The webhook didn't fire.” The automatic message never came, so our side didn't know anything happened.
“We're polling instead.” We keep asking “anything new?” over and over, because there's no webhook.
“Can this service tell us when something happens, or do we have to keep checking?”

