A webhook is an automatic message one system sends to a web address you choose the moment a specific event happens, such as a new order or a failed payment.
Integration · Reviewed by Ray Rasouli
Ask about webhook
Plain answers, with your setup in mind.
Ask anything about webhook. For example, how it works in your current tools.
A scripted guide for now. It does not store what you type.
With a regular API, your system has to keep asking, "Anything new?" A webhook flips that around: the other system tells you when something happens. It is the difference between checking your mailbox every hour and getting a text when a package arrives.
A retailer's online store might send a webhook to the warehouse app each time an order is paid, so picking starts right away instead of waiting for the next scheduled sync.
Webhooks are fast and efficient, but the receiving side must be ready to catch them, check they are genuine and handle the same message arriving twice.
The usual flow, step by step.
In practice
The receiving endpoint is down.
If your server is offline when the message arrives, the event can be lost unless the sender retries.
Duplicate events are processed twice.
Senders often retry, so the same order can be created twice without a duplicate check.
Messages are not verified.
Without checking the signature, anyone who finds the address could send fake events.
Events arrive out of order.
An update can show up before the create, which confuses systems that expect a neat sequence.
With an API, you ask for data when you want it. With a webhook, the other system pushes data to you when an event happens.
They can be. Use HTTPS, verify the signature the sender includes, and keep the receiving address private.
A 30-minute discovery call with Ray, then a clear list of what to fix first. No obligation.
With Ray Rasouli. No obligation.