HomeDocsEmbed the Inspector
Free embed · No API key

Drop a live webhook tester
into your blog or docs

One iframe tag, working webhook demo. Generates a real URL, captures real requests in real time. Free for technical writers, tutorial authors, and documentation sites — no signup, no API key, no rate-limit-by-domain.

Live demo — this is the embed

The block below is rendered from /embed/inspector — the same iframe you can paste in your post.

Get your snippet

Pick a provider to pre-load its sample payloads alongside the inspector, or leave it on Generic for the inspector alone.

HTML — for blogs, docs, plain pages
<iframe
  src="https://webhookwhisper.com/embed/inspector"
  width="100%"
  height="560"
  loading="lazy"
  title="Live webhook inspector"
  style="border:0; border-radius:12px; max-width:900px;"
></iframe>
Markdown one-liner — for dev.to, GitHub READMEs
<iframe src="https://webhookwhisper.com/embed/inspector" width="100%" height="560" loading="lazy" title="Live webhook inspector" style="border:0;border-radius:12px;max-width:900px;"></iframe>

With provider pre-loaded — ?provider=stripe

Side-by-side: live URL on the left, Stripe Test Sender on the right. Reader copies the URL, fires a sample event, and sees it land — all without leaving your post.

Why embed instead of linking out

Readers stay on your post

Linking to an external tool loses ~40% of readers — the third-party tab steals attention. Embedded demos keep the entire experience under your URL.

Zero maintenance

You don't host anything. We handle uptime, SSL, the WebSocket layer, all 80 sample payloads, signature verification recipes — everything inside the iframe is our problem.

Real, not screenshots

Tutorials with screenshots age badly. An embedded live tool stays current automatically — when we add a provider or fix a bug, every embed picks it up immediately.

URL parameters

ParamTypeEffect
providerslugPre-loads the Test Sender for that provider next to the inspector. One of stripe, github, shopify, twilio, slack, sendgrid, paypal, razorpay, and 28 more — see all providers.
hideAttributionflag (=1)Hides the "Powered by WebhookWhisper" footer. Allowed but please leave on by default — the attribution is what funds the free embed.

Recommended iframe attributes

<iframe
  src="https://webhookwhisper.com/embed/inspector?provider=stripe"
  width="100%"
  height="640"
  loading="lazy"               <!-- don't block LCP -->
  title="Live webhook inspector"
  style="border:0; border-radius:12px; max-width:900px;"
></iframe>

Frequently asked questions

Is the embed actually free?
Yes. There is no API key, no rate-limit-by-domain, no signup wall. Each visitor to the host page gets their own ephemeral webhook URL (1-hour TTL, 50 events) just like the homepage demo. The only cost to us is the same per-visitor cost we pay anyway when someone visits webhookwhisper.com directly.
Does it work without JavaScript?
No. The inspector is a real-time tool — it opens a WebSocket back to webhookwhisper.com to stream incoming webhook events. Without JS the iframe will render an empty container. If your readers have JS disabled, link to https://webhookwhisper.com instead of embedding.
What gets logged when a reader uses my embed?
Same as the regular homepage demo: the visitor's IP (used for guest-session rate limits), the User-Agent, and any webhook payloads they receive at their generated URL. We do NOT pass referrer information back to you, and the embed does not set tracking cookies that follow the reader off webhookwhisper.com. The iframe is sandboxed by the browser to its own origin.
Can I customize the look or hide the WebhookWhisper branding?
The embed inherits the same color palette as the rest of webhookwhisper.com — there is no theme parameter today. The "Powered by WebhookWhisper" attribution at the bottom of the iframe can be hidden with ?hideAttribution=1 if your editorial guidelines require it, but we ask that you keep it visible by default — the embed is free precisely because the attribution is the unit of distribution.
Does this hurt my Lighthouse / Core Web Vitals score?
The iframe is lazy-loadable (loading="lazy" attribute supported by all modern browsers — see the snippets below). With lazy loading the embed contributes ~0 to your LCP and INP scores. The bundle size of the inspector itself is ~120 KB gzipped — only loaded when the iframe scrolls into view.
Can I embed this in a Notion page / Medium article / dev.to post?
It depends on the platform. dev.to supports raw HTML embeds via the {% embed %} liquid tag. Medium does not allow arbitrary iframes for free accounts. Notion supports iframes via /embed blocks. Substack supports iframes in paid posts. The simplest test: paste the snippet, see if it renders. If the platform strips the iframe, link to webhookwhisper.com instead.
What happens if the embed is loaded behind a corporate firewall that blocks WebSockets?
The webhook URL is still generated and the visitor can still copy it and send requests to it from anywhere. Only the real-time stream of "you got a new event" notifications inside the iframe will be silent. The events themselves are captured server-side and visible after a page refresh.
Can I embed this in a commercial product / paid course?
Yes — that's explicitly fine. The embed is free for all uses, commercial or otherwise. We just ask that the "Powered by WebhookWhisper" attribution stay visible (the default).

Related

API Reference

Manage endpoints, query events, and configure forwarding rules programmatically.

Verifying WebhookWhisper Signatures

How to verify the X-WebhookWhisper-Signature header in 6 languages.

Webhook Signature Playground

In-browser HMAC compute & verify for Stripe, GitHub, Shopify, Slack.

Webhook Provider Directory

Test payloads from 36 providers — Stripe, GitHub, Shopify, Twilio…

Webhook Glossary

30 atomic terms — replay attack, idempotency key, signature header, etc.