Webhook Signature Verification (HMAC-SHA256) in Node, Python, Ruby — 2026 Guide

Apr 29, 2026 · 9:25 AM UTC ·8 min read · 0 reactions · 0 comments · 31 views

#webhooks #security #node.js #python #ruby

TL;DR · WeSearch summary

This article provides a comprehensive guide to implementing HMAC-SHA256 webhook signature verification in Node.js, Python, and Ruby, emphasizing the importance of security in validating incoming webhook requests. It highlights common implementation mistakes such as verifying after body parsing and using insecure comparison operators. The guide offers code examples and best practices to prevent attacks like replay and timing attacks across platforms like Stripe, GitHub, and Slack.

Key facts

▪Webhook signature verification prevents unauthorized POST requests from triggering sensitive actions like refunds or account creation.
▪A common error is verifying the signature after parsing the JSON body, which alters the raw data and causes mismatches.
▪Using constant-time comparison functions like crypto.timingSafeEqual or hmac.compare_digest is essential to prevent timing attacks.
▪Each environment and endpoint should use a unique signing secret stored in environment variables, not in source code.
▪The verification process requires the raw request body, HMAC-SHA256 computation with the secret, proper encoding, and secure header comparison.

About this source

DEV.to (Top) files mainly under programming. We currently carry 4,924 of its stories.

All DEV.to (Top) coverage →

Original article

DEV.to (Top)

Read full at DEV.to (Top) →

Story provenance

Source · retrieval · rights · ranking — open for full record

inspect →

Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.

Record

Original publisher	DEV.to (Top)
Canonical URL	https://dev.to/shotatanikawa/webhook-signature-verification-hmac-sha256-in-node-python-ruby-2026-guide-26m
Publication time	Wed, 29 Apr 2026 09:25:13 +0000
Retrieval time	2026-04-29T09:36:54.536Z
Last seen	2026-04-29T09:36:54.536Z
Headline source	Publisher (no WeSearch rewrite)
Excerpt source	publisher body
Excerpt method	First ~120 words (~800 chars) of extracted publisher body, fair-use limited.
Summary	WeSearch · cerebras-chat (WeSearch summarizer)
Summary source text	contentText
Citation coverage	Summary is a WeSearch-generated derivative; primary citation is the original publisher URL.
Cluster	Lk7IhzezsxMI
Cluster logic	Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison.
Ranking reason	Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking.
Publisher visit	Yes — open original
Substitutes article?	No — link-out required for full text

Rights status (four layers)

Publisher-declared

No publisher-confirmed rights record for this source yet.

Machine-readable

No source-specific machine-readable restriction detected beyond the public feed.

WeSearch interpretation

WeSearch declared handling (basis: Derived from the published RSS/Atom feed). This is WeSearch policy, not a legal grant on the publisher's behalf.

Unknown

Retrieval and training permissions are not asserted unless the publisher confirms them.

WeSearch handling by dimension

Indexing	May the item be indexed (stored, ranked, made findable)?	Allowed
Snippet	May a short excerpt of the publisher's text be shown?	Allowed
AI summary	May WeSearch generate its own short summary of the article?	Limited
Retrieval / RAG	May the content be exposed for third-party retrieval-augmented generation?	Not asserted
Model training	May the content be used to train AI models?	Not asserted
Commercial reuse	May the content be reused commercially?	Not permitted

Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.

Open original publisher → Source rights JSON → Machine-readable provenance → Rights framework → WESEARCH-STORY-PROVENANCE-V1

Opening excerpt (first ~120 words) tap to expand

try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3834635) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } ShotaTanikawa Posted on Apr 29 • Originally published at hookray.com Webhook Signature Verification (HMAC-SHA256) in Node, Python, Ruby — 2026 Guide #webhooks #node #python #security I review a lot of webhook handlers. Roughly 3 out of 5 either have a subtle signature-verification bug — or someone disabled verification entirely "to make it work." Both leave a public POST endpoint that anyone with the URL can fire fake events at.

…

Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).

Anonymous · no account needed

Discussion

0 comments