What is a webhook?

All about webhooks

A webhook is a lightweight, event-driven communication that automatically sends data between applications via HTTP. Triggered by specific events, webhooks automate communication between application programming interfaces (APIs) and can be used to activate workflows.

Because webhooks can connect event sources to automation solutions, they are 1 way to launch event-driven automation to perform IT actions when a specified event occurs.

How are webhooks different from an API?

Think of an API like ordering food by calling the restaurant every few minutes to ask, “Is my order ready yet?” You keep dialing until you get a “Yes!” answer.

A webhook, by contrast, is like giving the restaurant your phone number and asking them to call you the moment your food is done. You set it up once—hand over a special phone number (URL) and say “Call me when X happens”—and then you hang up. No more checking in. When that event occurs, the restaurant (server) simply rings you (sends a POST) with all the details.

Key differences

• Who does the work

  • API polling: You (the client) keep asking for updates.

  • Webhook push: The restaurant (server) calls you only when there’s news.

• Traffic and timing

  • Polling: Can waste time and bandwidth checking in when nothing’s changed.

  • Webhook: Instant, only one message when it matters.

• Relationship to each other

  • A webhook isn’t a replacement for an API—it needs an API behind it to define what “events” are possible and what data will be sent.

In short, APIs allow you to request information at any time; webhooks enable the server to notify you precisely when an event occurs.