Browser-side developer tool
Webhook HMAC-SHA256 Signature & Retry Backoff Simulator
Compute real Web Crypto HMAC-SHA256 webhook signatures, verify replay-window headers locally without sharing secrets, and plan jittered exponential backoff retry schedules.
1. Signing secret, payload & retry policy
2. Signature & backoff schedule
Computing...Exponential backoff retry schedule
| Attempt | Base Delay | Jitter Window | Cumulative | Action |
|---|
Questions developers ask
Is the HMAC-SHA256 digest real cryptographic output?
Yes. This tool uses your browser's native Web Crypto SubtleCrypto HMAC-SHA256 implementation so the generated hex and Base64 signatures match Node.js crypto and production gateways.
Why include a timestamp tolerance check when verifying webhooks?
Signing the Unix timestamp alongside the raw request body blocks replay attacks if an old captured payload is re-sent after your tolerance window (typically 300 seconds).
Which HTTP status codes should trigger exponential backoff retries?
Retry 429 rate limits, 408 timeouts, and 5xx server errors with jittered exponential backoff. Do not retry 400 or 401 failures because payload or signature defects will not self-heal.
Next step on APIDir
Compare verified provider pricing or list your API.
Pair these browser-side utilities with APIDir's source-linked pricing directory, Signals monitoring, and paid provider intake review.
Rate-Limit & Monthly Cost Calculator
Check peak RPM/TPM headroom, prompt cache savings, and retry spend.
Open tool →Browser ToolOpenAPI 3.1 & cURL Snippet Builder
Generate OpenAPI YAML, cURL, and TypeScript fetch snippets locally.
Open tool →ProvidersSubmit a provider for review
Request source-verified directory inclusion with our transparent review SLA and evidence checklist.
Submit provider →APIDir Delta · controlled rollout
Join the source-linked pricing update waitlist.
Confirm your address to join the waitlist. Editorial delivery starts only after sender, suppression, and evidence checks are active.