Update Webhook Signature Auth
Configure HMAC signature verification on inbound requests. The platform computes HMAC-<algo>(secret, raw_body) for every incoming request and compares against the value in the configured header — requests with missing or wrong signatures are rejected at the edge with 401.
This is the receiving side of webhook integrations: providers like Stripe, GitHub, or Shopify sign every webhook they send you with a shared secret, and this configuration lets you verify those signatures without writing code in your upstream service.
Pair the algorithm with the provider's expected scheme: hmac-sha256 for Stripe / GitHub, hmac-sha1 for legacy GitHub events. The header name varies (X-Hub-Signature-256, Stripe-Signature, X-Shopify-Hmac-SHA256) — set it to whatever the provider sends.
Path parameters
Request body
X-Hub-Signature-256 (GitHub), Stripe-Signature (Stripe — note Stripe wraps in t=...,v1=... format), X-Shopify-Hmac-SHA256 (Shopify).hmac-sha256 (default) or hmac-sha1. Anything else returns 400.Response (200 OK)
Empty body on success.
Errors
algo (only hmac-sha256/hmac-sha1 accepted).