Webhook
Definition
A webhook is an automatic HTTP request a platform sends to a URL you choose the moment something happens, such as a new order or a stock drop. It pushes data to your other systems in real time instead of making them ask repeatedly for changes. Each call carries a signature so the receiver can verify it came from the platform.
Why it matters for your store
Most stores are connected to something else: an accounting tool, a warehouse, a CRM, a spreadsheet someone maintains. Without webhooks those systems either poll the store every few minutes, which is wasteful and still late, or someone copies data by hand. With webhooks, a new order appears in the accounting tool seconds after it is placed.
Webhooks also run the other way. Payment providers, carriers, marketplaces, and invoice integrators all send webhooks to the store to report a payment result, a delivery, a new order, or an accepted invoice. A platform's handling of incoming webhooks, verifying signatures and ignoring duplicates, is as important as what it sends.
How Kambloo handles it
In the admin panel you register a webhook subscription with a target URL, the events you want, and a secret. Available events cover the order lifecycle (created, paid, shipped, cancelled), product changes (created, updated, deleted), new customers, and low stock. Each delivery is a JSON POST signed with an HMAC-SHA256 header that your server verifies with the secret.
Failed deliveries are retried five times with exponential backoff. An endpoint that fails continuously for three days is paused automatically and you are notified. The panel shows the last 100 deliveries with request and response summaries and a button to resend any of them.
Incoming webhooks from payment providers, marketplaces, carriers, and invoice integrators arrive at a central endpoint per store, are verified by signature before anything is processed, and are deduplicated by event ID, so a provider retry never creates a second order or a double payment record.
Questions about Webhook
What is the difference between a webhook and an API?
With an API, your system asks the platform for data when it wants it. With a webhook, the platform tells your system when something happens. Most integrations use both: webhooks to learn about events, the API to act on them.
What happens if my server is down when a webhook is sent?
Kambloo retries five times with increasing delays. If an endpoint keeps failing for three days it is paused and you are notified. Every delivery is logged and can be resent by hand.