Requex.me LogoRequex.me

Documentation

Browse by section

Keep all guides, tool docs, automation recipes, and comparison pages in one navigable place.

Docs Home
Docs

Foundation docs for getting started fast, understanding key terms, and tracking what has changed.

Guides

Start with fundamentals, then move into provider-specific webhook testing and production hardening.

Tool Docs

These pages explain what each tool does, when to use it, and how it fits into a webhook debugging workflow.

Automation Docs

Use these setup guides when you want forwarding rules, custom responses, security checks, or multi-destination fanout.

Compare

Use these pages to compare developer workflows, pricing tradeoffs, and feature differences between webhook tools.

Secure Webhook Endpoints with Auth Validation

Add industry-standard authentication to any Requex endpoint. Reject unauthorised callers, log every attempt — including failures — and forward only valid requests downstream.

Editorially reviewed by the Requex team7 min readAbout the product

Short answer: In Requex Settings → Auth, choose your method (HMAC, Bearer, API key, Basic, or Custom), paste your secret, and save. Requex now validates every inbound request. Failed attempts are logged with the label auth_failed so you can audit them without losing the data.

Supported Auth Methods

MethodHow it worksUse with
BearerChecks Authorization: Bearer <token> headerInternal APIs, custom services
HMACComputes HMAC(secret, rawBody) and compares signature headerStripe, GitHub, Shopify
API KeyReads a named header or query param, compares to expected valueAny service with API key auth
BasicDecodes Authorization: Basic base64, compares username + passwordLegacy services, simple setups
CustomReads any header, query param, or body dot-pathNon-standard auth schemes

HMAC Configuration — Stripe Example

Stripe signs every webhook with a HMAC-SHA256 signature in the Stripe-Signature header. To validate it in Requex:

FieldValue
Auth methodHMAC
Algorithmsha256
Signature headerStripe-Signature
Signature prefixv1=
Secretwhsec_... (from Stripe Dashboard)

Requex captures the raw request body before JSON parsing — required for HMAC verification to work correctly. The raw bytes are used as the HMAC message, matching how Stripe computes the signature on their end.

What Happens on Auth Failure

When a request fails auth, Requex:

  1. 1. Saves the full request to your log with label auth_failed
  2. 2. Emits a real-time Socket.IO event so you see it live in the dashboard
  3. 3. Optionally adds a WWW-Authenticate header (if simulateChallenge is on)
  4. 4. Returns 401 or 403 to the caller
  5. 5. Does not trigger forwarding rules — invalid requests don't reach your downstream services

Add auth to your webhook in 2 minutes

Free, no signup. Open Requex, configure auth, and you're protected.

Open Requex →

Related use cases

Start Testing Webhooks Now

Generate your unique URL and test webhooks instantly. Free, no signup.

Open Webhook Tester →