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

---

## Technische Erklärung

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.

## Geschäftliche Relevanz

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.

## Implementierungsbeispiel

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.

## Einschränkungen und häufige Missverständnisse

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.

## Themen

Systemarchitektur Intelligente Automatisierung Cybersicherheit

## Quellen

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

## Besprechen Sie Ihre Systeme

Benötigen Sie Hilfe bei der Implementierung oder Bewertung dieses Konzepts? Keenfunnel entwirft vernetzte KI-, Automatisierungs- und Datensysteme.

Discovery-Session buchen