# Webhook
**Source:** https://glossary.keenfunnel.com/terms/webhook
**Language:** Hindi

---

## तकनीकी स्पष्टीकरण

The producer sends a payload—commonly JSON—to a subscriber endpoint when a defined event occurs. Production implementations require event identifiers, authentication or signatures, timeouts, retries, idempotent processing, ordering assumptions, observability, and a strategy for dead-letter or failed deliveries. Webhooks enable push-based integration rather than repeated polling.

## व्यावसायिक प्रासंगिकता

Webhooks reduce latency and unnecessary API requests in connected workflows. They are commonly used to trigger fulfilment, synchronise records, start automation, and notify downstream services.

## कार्यान्वयन उदाहरण

A payment platform sends a signed webhook after a successful payment. The receiving service verifies the signature, checks the event ID for duplicates, updates the order, and queues fulfilment.

## सीमाएँ और आम गलत धारणाएँ

Webhook delivery is generally not equivalent to exactly-once processing. Requests can be duplicated, delayed, reordered, or lost after retry limits. Public endpoints also create an attack surface and must not trust payloads without verification.

## विषय

सिस्टम आर्किटेक्चर इंटेलिजेंट ऑटोमेशन साइबर सुरक्षा

## स्रोत

Standard Webhooks specification — GitHub Docs — Webhooks — https://docs.github.com/en/webhooks

## अपने सिस्टम पर चर्चा करें

इस अवधारणा को लागू करने या मूल्यांकन करने में मदद चाहिए? कीनफ़नेल कनेक्टेड एआई, स्वचालन और डेटा प्रणालियाँ डिज़ाइन करता है।

एक डिस्कवरी सत्र बुक करें