How apps tell each other things, in plain words
How business apps send each other events
Webhooks are the automatic messages one app sends another when something happens, like a paid invoice or a new order. These pages explain what's inside them, what the response codes mean, and what happens when one is missed. Everything is written for people who run a business, not for developers.
All the notes
What Is a Webhook?What it means when a business app says it supports webhooks, and how one app tells another that something just happened.
Webhook or API Polling: What Is the Difference?Why some apps push updates to you while others make you wait or refresh, and what polling an API means next to a webhook.
What Is Inside a Webhook RequestWhat the URL, headers and payload in a webhook request contain, using examples from Stripe, GitHub and Shopify documentation.
Reading a Webhook Payload and JSONHow to read the data an app sends in a webhook, from JSON basics to finding the event type and the record that changed.
Common Webhook Events in Business AppsWhat kinds of events, such as a new order or a paid invoice, can trigger a webhook, with examples from Shopify, Stripe and GitHub.
Webhook Response Codes ExplainedWhat the status codes 200, 400, 404 and 500 mean when a webhook delivery fails, and what to check first for each one.
Webhook Retries and Failed DeliveriesWhat happens when your receiving system is down and a webhook is missed, with retry rules from Stripe and GitHub.