Glossary · web
Webhook
Definition
A webhook is a way for a system to send an automatic HTTP request to another system when an event happens. Instead of polling, it 'pushes' — Stripe sends a webhook when payment completes, GitHub when a PR opens, Trendyol when an order arrives.
Detailed explanation
A webhook is simple: when an event occurs, the provider sends an HTTP POST to a registered URL. The developer only writes one endpoint, the provider calls it on every event.
Difference vs API: API is pull, webhook is push. With API the client keeps asking 'any orders?'; with webhook the provider says 'an order arrived'. More efficient, real-time, lower server load.
Examples: Stripe on payment success, Trendyol on order, GitHub on PR open, WhatsApp Business on message, n8n on automation trigger — all push webhooks.
Use cases
→Process orders when payment completes
→Auto-reply when new email arrives
→Trigger deploy when GitHub PR opens
→Update stock when marketplace order arrives
→Notify result when AI agent tool finishes
Pros
- +Real-time (no 5-min polling delay)
- +Server-resource efficient
- +Natural fit for event-driven architecture
- +Easy 3rd-party integration
Cons
- −Public endpoint required (auth + rate limit critical)
- −Idempotency check (webhook can fire twice)
- −Retry + dead-letter queue needed
- −Hard to debug (event-driven nature)
Related terms
Related services
Planning a project around Webhook?
In a 30-minute discovery call we share a written architecture + cost + team recommendation tailored to your project.
Start a discovery call