An event starts the communication
A webhook lets a system send a message to a configured endpoint when an event occurs. This differs from repeatedly asking an API whether something changed. The message can contain event details or identifiers that the receiving integration uses to request further information.
GitHub’s webhook documentation illustrates this delivery model. For business systems, the same pattern can connect an order event, payment update or form submission to the next appropriate action.
Example: updating a job after payment
Imagine a payment provider sends an event that an invoice has been paid. The receiving system verifies the message, identifies the corresponding job and updates its payment status. It may then create a task for staff to review scheduling. The workflow should act on the verified business event, rather than trusting a customer’s browser returning to a success page.
Record the event identifier and processing result. If the same event arrives again, the system should recognise the previous work instead of creating another task or repeating a customer notification.
Plan for delivery failures and duplicates
Webhook behaviour varies by provider. Stripe, for example, documents duplicate deliveries, retries and events arriving out of order. Its webhook guidance also covers signature verification. Design against the actual provider’s contract rather than assuming every event arrives once and immediately.
- Verify the sender using the provider’s supported method.
- Validate the payload and expected event type.
- Make repeated processing safe for the intended action.
- Record failures and provide a controlled way to retry.
- Alert the responsible team when processing stops working.
Return an appropriate response promptly and separate slow downstream work where necessary. An integration is useful only when someone can determine whether an event was received, processed or left waiting for attention.
Common questions about webhook
Is a webhook the same as an API?
They work together but describe different interaction patterns. An API often receives requests for data or actions; a webhook delivers a notification when an event happens.
Does receiving a webhook prove its contents are genuine?
No. A public endpoint can receive other requests. Verify the message through the provider’s supported mechanism and validate it before changing records or triggering actions.
Related definitions
- API — An application programming interface: an agreed way for software systems to request data or trigger actions in another system.
- API integration — A connection that uses software interfaces to exchange information or coordinate actions between systems, with authentication, validation and error handling.
- Automation — A repeatable sequence of actions triggered by a rule, event or schedule. Reliable automation includes validation, error handling and a clear human owner.
- HTTP status code — A response code communicating the result of a request. Examples include 200 for a successful response, 301 for a permanent redirect and 404 for a resource not found.
Related SEO guides
A webhook can pass enquiry events to another system, with retries and duplicate handling that keep lead measurement trustworthy.
For help connecting these decisions with your website, explore our SEO services or start with an SEO audit.
Put it into practice
Explore our api integration service or talk with Refined IT about applying this to your website or business systems.