{
  "id": 20672962,
  "title": "Polling Before Webhooks for Auditable SMS Delivery Records in Node.js Logistics Systems",
  "url": "https://urgent.news/2026/11/18/polling-before-webhooks-for-auditable-sms-delivery-records-in-node-js",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-11-18T23:29:00.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/fluxh91/polling-before-webhooks-for-auditable-sms-delivery-records-in-nodejs-logistics-systems-1kom"
  },
  "original_language": "en",
  "account": "Node.js logistics systems demand an auditable SMS delivery record to satisfy compliance requirements. This necessitates polling before webhooks for establishing an evidence trail. The record must include information about the intent to send, acceptance by the external service, and subsequent delivery evidence observed by the application. A single mutable status field is insufficient to explain complex scenarios like operator corrections or retries. Instead, assign an internal notice identifier, associate it with the notice text and intended destination, and persist the submission outcome separately from observations. The external message identifier should be retained when available, along with sufficient adapter context to interpret it later. Corrections should result in new notice attempts linked to the original intent to avoid confusion. The distinction between observations and conclusions is crucial; store the external status as observed, the time received, and any external event time if provided. Derive the application's conclusions from these records using a documented mapping. Uncertainty should be queryable, allowing for reconciliation work without silently asserting success or triggering another SMS. The integration design should be based on the evidence boundary. Polling involves selecting outstanding notice attempts, retrieving status through an adapter, recording the observation durably, and scheduling further checks according to policy. Webhooks move the receiving boundary into the application, requiring authentication, storage of observations, and acknowledgment only after a durable handoff succeeds. Establish the actual rules for retries, event identifiers, ordering, and replay before deployment. This record design, independent of the programming language, models observations rather than network clients. The provided Python example illustrates the concept, emphasizing the importance of preserving raw observations for later mapping changes and retention obligations. Comparing polling and webhooks reveals that existing infrastructure may favor polling if a durable scheduled worker is available, while webhooks are suitable when an authenticated public receiver is present and faster delivery is required. The choice depends on existing infrastructure and timing requirements.",
  "summary": "A logistics compliance notice needs a delivery record that survives the process that sent it. That constraint changes an SMS API comparison: a convenient send call contributes little if the application cannot later explain which notice it submitted, which status it observed, and what evidence remains missing. Start with the record. Short answer: choose polling first for a Node.js logistics…",
  "key_points": [
    "Polling before webhooks required for auditable SMS delivery records",
    "Internal notice identifier assigned for complex scenarios",
    "External message identifier retained with adapter context"
  ],
  "editors_take": null,
  "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."
}