Skip to content
dvnt.io

Resources · glossary

Webhook

The reverse of a normal request: the external system notifies yours itself when something happens. That way a payment status shows up instantly, without polling every minute.

Also called
  • webhooks
  • HTTP callback
  • event notification
  • web callback
  1. 01

    Why you would want one

    Because the alternative is asking “is it done yet?” over and over. With one order it makes no difference; with a thousand a day, polling creates traffic, delays and costs that a webhook does not have.

  2. 02

    Where you come across it

    A payment gateway confirming a transaction, a courier updating a shipment status, a warehouse system reporting a stock change. In practice most e-commerce integrations rely on this mechanism.

  3. 03

    What it needs on your side

    An address reachable from the internet that will accept the notification, and resilience to repeats: providers send the same event several times when they get no acknowledgement. Without safeguards this ends in duplicate orders.

  4. 04

    What people forget

    What happens when your server happens not to respond. Good integrations queue undelivered notifications; with poor ones the event is simply lost, and the mismatch comes out at stocktaking.

In practice

Related terms

  • APIAn agreed way for one system to ask another for data or tell it to do something. APIs are how a shop knows its stock levels and how a website sends a contact to the CRM.
  • CacheA stored result of earlier work, served instead of doing the work again. The cheapest way to speed up a website and the most common reason for the question “why can't I see my changes”.

← All terms

15 minutes. No sales pitch.

A term in a proposal sounds foreign? In 15 minutes we explain what it means for your project.