MG Software.
HomeAboutServicesPortfolioBlog
Contact Us
  1. Home
  2. /Knowledge Base
  3. /What is a Webhook? - Explanation & Meaning

What is a Webhook? - Explanation & Meaning

Learn what webhooks are, how HTTP callbacks work for event-driven integrations, and why webhooks are essential for real-time notifications.

Definition

A webhook is an HTTP callback that automatically sends a message (HTTP POST request) to a specified URL when a specific event occurs. Webhooks enable real-time, event-driven communication between systems without the need for continuous polling.

Technical explanation

Webhooks follow a publisher-subscriber model: a source service (publisher) sends an HTTP POST request with a JSON payload to a receiver-specified endpoint (subscriber) when an event occurs. Examples include a payment provider sending a webhook on a successful payment, or GitHub triggering a webhook on a push to a repository. Security is crucial: webhooks must be verified via HMAC signatures (a hash of the payload with a shared secret) to prevent malicious actors from sending fake events. Retry mechanisms with exponential backoff ensure reliable delivery during temporary receiver failures. Idempotent handling prevents an event from being processed multiple times when the same webhook is resent. Webhook queues (via message brokers like RabbitMQ or Redis) decouple receipt from processing for better scalability. Monitoring webhook delivery with dashboards for success rates and failure ratios is essential. The difference with polling is fundamental: with polling, the receiver repeatedly asks for updates (wastes resources), with webhooks, the source proactively sends updates (efficient and real-time).

How MG Software applies this

MG Software implements webhooks as a standard integration mechanism in the applications we build. We use webhooks for payment notifications (Stripe, Mollie), CI/CD triggers (GitHub), CRM synchronization, and real-time data updates between systems. All webhook endpoints are secured with HMAC signature verification and equipped with retry logic and idempotent processing.

Practical examples

  • An online store receiving a Stripe webhook on a successful payment, after which the order is automatically confirmed, an invoice generated, and a shipping label created.
  • A CI/CD pipeline that is automatically triggered by a GitHub webhook on every push to the main branch, without the system needing to continuously poll the repository.
  • A marketing automation receiving real-time notifications via HubSpot webhooks when a lead fills out a form, after which a personalized follow-up email is sent within seconds.

Related terms

api first developmentcontinuous deploymenterpcrmfeature flags

Further reading

What is API-First Development?What is Continuous Deployment?What is CRM?

Related articles

What is an API? - Definition & Meaning

Learn what an API (Application Programming Interface) is, how it works, and why APIs are essential for modern software development and system integrations.

What is a REST API? - Definition & Meaning

Learn what a REST API is, how the RESTful architecture principle works, and why REST APIs are the standard for web services and system integrations.

What is a Message Queue? - Definition & Meaning

Learn what a message queue is, how async communication works with RabbitMQ and Kafka, and why message queues are essential for scalable systems.

API Integration Examples - Practical Integrations for Businesses

Discover practical API integration examples for businesses. Learn how REST APIs, webhooks, and middleware streamline your business processes and automation.

Frequently asked questions

With polling, your application repeatedly asks (for example every 30 seconds) an external service if there is new data. This wastes resources when there are no updates. With webhooks, the external service proactively sends a message to your application as soon as something changes. Webhooks are more efficient, real-time, and significantly reduce server load.
Verify incoming webhooks via HMAC signatures: the sender computes a hash of the payload with a shared secret and includes it in a header. Your endpoint recomputes the hash and compares it. Additionally: use HTTPS, validate the payload structure, implement IP whitelisting if possible, and process webhooks idempotently to prevent duplicate processing.
Good webhook implementations include retry mechanisms with exponential backoff: if the first attempt fails, it retries after 1 minute, then after 5 minutes, 30 minutes, and so on. Some providers offer a webhook log where missed events can be resent. It is wise to use a message queue that buffers incoming webhooks for asynchronous processing.

Ready to get started?

Get in touch for a no-obligation conversation about your project.

Get in touch

Related articles

What is an API? - Definition & Meaning

Learn what an API (Application Programming Interface) is, how it works, and why APIs are essential for modern software development and system integrations.

What is a REST API? - Definition & Meaning

Learn what a REST API is, how the RESTful architecture principle works, and why REST APIs are the standard for web services and system integrations.

What is a Message Queue? - Definition & Meaning

Learn what a message queue is, how async communication works with RabbitMQ and Kafka, and why message queues are essential for scalable systems.

API Integration Examples - Practical Integrations for Businesses

Discover practical API integration examples for businesses. Learn how REST APIs, webhooks, and middleware streamline your business processes and automation.

MG Software
MG Software
MG Software.

MG Software builds custom software, websites and AI solutions that help businesses grow.

© 2026 MG Software B.V. All rights reserved.

NavigationServicesPortfolioAbout UsContactBlog
ResourcesKnowledge BaseComparisonsExamplesToolsRefront
LocationsHaarlemAmsterdamThe HagueEindhovenBredaAmersfoortAll locations
IndustriesLegalEnergyHealthcareE-commerceLogisticsAll industries