DashForDevsDocs
DocsNewsAPI v1
dashfordevs.comSign in

© 2026 DashForDevs

DocsNewsdashfordevs.comLegalStatus
DocsSecurityWebhook Signatures
Introduction
Getting Started
Authentication
Products
Categories
Cart
Checkout
Blog
Reviews
Webhooks
Customers
Orders
Inventory
Shipping
Discounts
Affiliates
Email
Media & Files
Analytics & Tracking
Locations
Tax
Global Data
SEO
Error Handling
Geography
Finance
Automations
Page Types
Surveys
Billing & Subscriptions
Storefront Payments
SDK Reference
REST API
Storefront Architecture
Notifications
Security
API Key SecurityCORS & Allowed OriginsWebhook SignaturesCustomer DataRate Limiting
Team & Permissions
Migrations & Import
Calendar & Appointments
Contact Forms
AI Bots
Dashboard API
Deployment
Changelog
Troubleshooting
Recipes
CLI & Deployment
Image Pipeline
White-label Platforms
Records Engine
Platform Modules
Platform Security
Site Keys & Client Sites
Use Cases
Operations

Webhook Signatures

Verify webhook payloads with HMAC signatures.

Updated March 29, 2026

On this page
  • Overview
  • Verification Flow
  • Next Steps

Overview

Every webhook request is signed with HMAC-SHA256. Always verify signatures to prevent spoofed requests. See Verifying Signatures for implementation details.

Verification Flow

  1. Read the raw request body
  2. Read the x-dash4devs-signature header
  3. Compute HMAC-SHA256 of the body using your webhook secret
  4. Compare using constant-time comparison
typescript
import crypto from "crypto"

const expected = crypto.createHmac("sha256", WEBHOOK_SECRET).update(body).digest("hex")
const valid = crypto.timingSafeEqual(Buffer.from(signature), Buffer.from(expected))

Next Steps

  • Verifying Signatures — Full implementation
  • Webhook Overview — Setting up webhooks
PreviousCORS & Allowed OriginsNextCustomer Data

On this page

  • Overview
  • Verification Flow
  • Next Steps