Glossary
Webhook
A webhook is an automated message one system sends to another when something happens (an order placed, a form submitted, a payment received), so the receiving system can react immediately instead of checking repeatedly.
Glossary
A webhook is an automated message one system sends to another when something happens (an order placed, a form submitted, a payment received), so the receiving system can react immediately instead of checking repeatedly.
With an API, your system asks; with a webhook, the other system tells you. That inversion is what makes near-real-time automation possible without constant polling.

Checking every minute for an event that happens twice a day means thousands of pointless requests, and still a delay of up to a minute. A webhook arrives when the event does.
Messages can arrive twice, arrive out of order, or fail to arrive if the receiver is briefly down. Production integrations handle duplicates safely, verify the message really came from the sender, and provide a way to recover missed events.
A well-built one catches up; a fragile one silently loses the events.
That depends on the sender. Good ones retry with backoff; others send once and forget. A robust integration assumes delivery is unreliable and provides a reconciliation path to catch anything missed.
Only if verified. A webhook endpoint is a public URL, so the receiver must confirm the message genuinely came from the expected sender (usually through a signature) before acting on it.
A webhook is an automated message one system sends to another when something happens (an order placed, a form submitted, a payment received), so the receiving system can react immediately instead of checking repeatedly.