Backend

Webhooks

HTTP callbacks that automatically send real-time data to other applications when specific events occur, enabling event-driven integrations.

Webhooks are user-defined HTTP callbacks that are triggered by specific events. When an event occurs in a source system, it sends an HTTP POST request to a configured URL with event data, enabling real-time communication between applications.

Unlike polling (repeatedly checking for changes), webhooks are push-based — the source system notifies you immediately when something happens. This is more efficient and provides near-instant updates.

Common webhook use cases include payment notifications (Stripe sends a webhook when a payment succeeds), CI/CD triggers (GitHub sends a webhook on push to trigger a build), and chat integrations (Slack incoming webhooks for sending messages).

Best practices include verifying webhook signatures (to ensure the request is authentic), responding quickly with a 200 status (process asynchronously if needed), handling retries and idempotency (webhooks may be sent more than once), and securing the endpoint (HTTPS, IP whitelisting).

Related Terms

REST API Event-Driven Architecture Microservices

Related Articles

I Tested 5 LLM APIs for Latency — Here's the Real Data (March 2026)
Mar 7, 2026
GPT-5.4 Is Here? No. But Here's What Developers Actually Need to Know About GPT-5
Mar 6, 2026

Want to learn more?

Explore more developer terms or read in-depth articles on the blog.

Browse all terms