{
  "id": 21199503,
  "title": "Sending a Webhook Is Easy. Delivering It Reliably Is the Hard Part.",
  "url": "https://urgent.news/2026/11/22/sending-a-webhook-is-easy-delivering-it-reliably-is-the-hard-part",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-11-22T10:41:29.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/quarj0/sending-a-webhook-is-easy-delivering-it-reliably-is-the-hard-part-575c"
  },
  "original_language": "en",
  "account": "A webhook initially appears as a straightforward feature, where a backend makes an HTTP POST to another service upon certain events, like an order being paid or a booking confirmed. However, the receiving service often proves to be the complex part. Requests may timeout, events may be delivered twice due to processing issues, and acknowledgements may fail to return. These issues necessitate the implementation of a queue, retries, signatures, delivery history, and a method to investigate failures.\n\nThe author developed Hookstride to address these challenges. Initially, it served as a solution for routing webhooks between the author's own projects, but it soon evolved into a platform for reliable event delivery. Key features include automatic retries, signed requests, delivery logs, replay, and more.\n\nThe author clarifies several common pitfalls in webhook implementation:\n1. An HTTP request success does not guarantee the business action succeeded. The receiver should durably record the event before acknowledging it.\n2. A timeout does not indicate whether the receiver processed the event. The sender should expect retries and be prepared to handle duplicates.\n3. Immediate retrying can exacerbate failures. Bounded retries with backoff, along with sufficient diagnostic information, are recommended.\n4. Security is essential. If the receiver cannot verify the request signature, anyone with the URL could potentially send forged events.\n\nTo send a booking confirmation as a webhook using Python, the author provides an example. The process involves importing necessary modules, defining a function to send the booking confirmation, setting up the HTTPS receiving endpoint as a Hookstride destination, generating a project API key, and making a POST request to Hookstride's API endpoint with appropriate headers and JSON payload.\n\nHowever, the author emphasizes that Hookstride does not handle the business logic. The receiving side must still perform several tasks, including reading raw request bytes, checking X-Webhook-Timestamp for freshness, verifying X-Webhook-Signature using the destination's signing secret, and confirming the signed envelope's id and type agree with the identifying headers. The author stresses the importance of storing verified event IDs with unique constraints and committing durable handling before returning a 2xx status code. Duplicates should be processed safely, and the division of responsibility between the application and Hookstride is crucial for reliable event delivery.",
  "summary": "A webhook often starts out as a small feature. After an order is paid or a booking is confirmed, your backend makes an HTTP POST to another service. Done. Then the receiving service goes offline for a few minutes. A request times out. An event is delivered twice because the receiver processed it but the acknowledgement never made it back. Suddenly, that simple HTTP request needs a queue, retries,…",
  "key_points": [
    "Webhooks appear simple but receiving service is complex",
    "Challenges include timeouts, duplicates, failed acknowledgements",
    "Hookstride addresses these with retries, signatures, logs"
  ],
  "editors_take": "Outsourcing event delivery to specialized platforms shifts the burden of retry logic and security to third parties, but developers must still manage the critical business logic of idempotent processing.",
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}