{
  "id": 20978270,
  "title": "Marketplace Webhook Signature Check After Deploy With Raw Body Admission Controls",
  "url": "https://urgent.news/2026/11/21/marketplace-webhook-signature-check-after-deploy-with-raw-body",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-11-21T01:34:00.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/seraphinalyn7139/marketplace-webhook-signature-check-after-deploy-with-raw-body-admission-controls-1hg6"
  },
  "original_language": "en",
  "account": "When a webhook signature check fails after an Express deploy, the problem often lies in middleware consuming the raw body before the handler runs. To resolve this, preserve the raw request bytes before JSON middleware processes them, and verify those bytes before parsing. Re-serializing the parsed object after verification can alter the signed representation, so it's crucial to keep the original bytes intact. Always check the registered signing secret, as rotation can produce similar symptoms. Reject verification failures with a status that the sender treats as non-retryable, and log the error with the registration ID. This drill aims to separate refusal of legitimate events from downstream processing failures, allowing operators to identify the root cause and avoid inflating the acceptance count. Verification should occur after capturing the original request bytes, and the ordering of steps is critical. For testing, a Go sender can simulate events without modifying the production runtime. Before implementing changes, compare the active signing secret with the receiver's configuration to account for rotated secrets. Log verification failures with the registration ID attached to aid troubleshooting, but avoid sharing sensitive marketplace content in routine error reports.",
  "summary": "The page a marketplace team should rehearse is painfully specific: a webhook signature check starts failing after a deploy, platform events stop entering the backend, and the on-call must decide how much refused traffic the recovery budget can tolerate. Keep the admission path small. Capture the original request bytes before JSON middleware, verify those bytes, and parse only after verification…",
  "key_points": [
    "Preserve raw request bytes before JSON middleware processes them",
    "Verify original bytes before parsing to maintain signed representation",
    "Reject verification failures with non-retryable status"
  ],
  "editors_take": "Preserving original request bytes before middleware processing prevents signature mismatches and ensures that verification failures are accurately distinguished from downstream processing errors during marketplace webhook integrations.",
  "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."
}