[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"glossary-webhook-dev-tools::en":3,"gloss-cluster-webhook-dev-tools::en":20,"gloss-next-webhook-dev-tools::en":9},{"slug":4,"category":5,"name":6,"definition":7,"meta_desc":8,"faq":9,"schema_markup":9,"related":10},"webhook-dev-tools","dev-tools","Webhook","A webhook is a way for one system to notify another system in real time, the moment something happens, by sending an HTTP POST request to a URL the receiving system has registered in advance — the inverse of typical API usage, where a client repeatedly polls a server asking \"has anything changed yet?\" With webhooks, the server pushes a notification only when there's actually something to report, which is far more efficient than polling and delivers near-instant notification instead of the delay inherent in a polling interval. Nearly every major API-driven platform supports webhooks: Stripe fires a webhook when a payment succeeds, GitHub fires one when a pull request is opened, and Anthropic-adjacent SaaS tooling commonly uses webhooks to notify a downstream system when a long-running AI job (like a batch processing job) completes. Why it matters for AI\u002FSaaS builders: webhooks are the standard integration pattern for connecting independent systems in real time without either side needing to constantly poll the other — they're the backbone of automation platforms like Zapier and Make.com, and they're essential for anything event-driven, like updating a CRM the instant a Stripe payment fails, or kicking off downstream processing the moment a user completes onboarding. Because webhook endpoints are public URLs that accept arbitrary POST requests, correctly verifying the request's authenticity (typically via a signature check using a shared secret) is critical — an unverified webhook endpoint is a real security risk, since anyone who discovers the URL could send fake events. How it works: the receiving application registers a URL with the sending platform (often via a dashboard or API call) and specifies which events it wants to be notified about. When that event occurs, the sending platform sends an HTTP POST to the registered URL with a JSON payload describing the event; the receiving endpoint must respond quickly (typically within a few seconds) with a 2xx status code to acknowledge receipt, or the sender will retry with backoff, assuming delivery failed. Worked example: a SaaS company wants to grant a user access to a paid feature the instant they complete a Stripe checkout. They register a webhook endpoint `POST \u002Fwebhooks\u002Fstripe` with Stripe, subscribed to the `checkout.session.completed` event. When a customer pays, Stripe sends a POST request to that URL with a JSON payload like `{\"type\": \"checkout.session.completed\", \"data\": {\"object\": {\"customer_email\": \"user@example.com\", \"amount_total\": 4900}}}`. The endpoint verifies the request's Stripe signature header against their webhook secret to confirm it's genuinely from Stripe (not a spoofed request), then updates that user's account to `plan: \"pro\"` in their database and returns a `200 OK` — all happening within roughly a second of the actual payment, with zero polling required.","A webhook is an automated HTTP callback — one system sends a real-time notification to another the moment a specific event happens.",null,[11,14,17],{"slug":12,"name":13},"api-gateway","API Gateway",{"slug":15,"name":16},"ci-cd","Continuous Integration \u002F Continuous Deployment (CI\u002FCD)",{"slug":18,"name":19},"model-context-protocol","Model Context Protocol (MCP)",[21,25,28,30,33,36,39,42,45,46,49,52],{"slug":22,"category":5,"name":23,"updated_at":24},"agent","Agent","2026-08-24T02:46:36+00:00",{"slug":26,"category":5,"name":27,"updated_at":24},"ai-code-assistant","AI Coding Assistant",{"slug":12,"category":5,"name":13,"updated_at":29},"2026-08-24T02:46:37+00:00",{"slug":31,"category":5,"name":32,"updated_at":29},"api-versioning","API Versioning",{"slug":34,"category":5,"name":35,"updated_at":24},"autonomous-agent","Autonomous Agent",{"slug":37,"category":5,"name":38,"updated_at":29},"blue-green-deployment","Blue-Green Deployment",{"slug":40,"category":5,"name":41,"updated_at":29},"canary-deployment","Canary Deployment",{"slug":43,"category":5,"name":44,"updated_at":29},"chaos-engineering","Chaos Engineering",{"slug":15,"category":5,"name":16,"updated_at":24},{"slug":47,"category":5,"name":48,"updated_at":29},"circuit-breaker","Circuit Breaker",{"slug":50,"category":5,"name":51,"updated_at":29},"cli","Command-Line Interface (CLI)",{"slug":53,"category":5,"name":54,"updated_at":29},"cloud-development-environment","Cloud Development Environment (CDE)"]