How MockFlow Webhook Debugging Works
Three steps from sign-up to a fully inspected webhook request.
Create a Request Catcher
Sign in to MockFlow, open a project, and create a Request Catcher. You get a permanent public URL like api.mockflow.io/your-project--id/catch/abc.
Point Your Webhook at It
Paste the URL into Stripe, GitHub, Shopify, Slack, or any service that sends HTTP webhooks. Fire a test event.
Inspect Every Detail
The full request appears in real time — method, status, headers, parsed JSON body, raw body, query string, IP address, and user agent.
Debug Any Webhook in Seconds
Once you have your catcher URL, test it immediately with cURL. No configuration, no server, no code.
# Send a test webhook request to MockFlow
curl -X POST https://api.mockflow.io/my-project--abc123/catch/xyz \
-H "Content-Type: application/json" \
-H "X-Webhook-Secret: your-secret" \
-d '{
"event": "payment.succeeded",
"amount": 4999,
"currency": "usd"
}'
# MockFlow captures and displays:
# - Method: POST
# - Headers: Content-Type, X-Webhook-Secret, ...
# - Body: { event, amount, currency }
# - IP address, User-Agent, timestampStripe Webhook Example
Use your MockFlow catcher URL as the Stripe webhook endpoint to capture real events before your backend is ready.
# Using Stripe CLI to forward to MockFlow stripe listen --forward-to \ https://api.mockflow.io/my-project--abc123/catch/xyz # Or add it in Stripe Dashboard: # Developers → Webhooks → Add endpoint # Endpoint URL: https://api.mockflow.io/my-project--abc123/catch/xyz
Everything You Need to Debug Webhooks
Full Request Inspection
View method, path, status code, every header, parsed JSON body, raw body, query string, IP address, and user agent — all in one place.
Real-Time Updates
The console updates every few seconds as new requests arrive. No manual refresh needed.
Replay to Any URL
Re-send any captured request to your localhost, staging server, or any URL. Test your handler without waiting for the provider to send another event.
Configurable Response
Customize the JSON body that MockFlow sends back to the webhook provider. Useful for providers that check response content.
Sensitive Header Masking
Authorization, cookie, and secret headers can be masked in the inspector to protect credentials when sharing or screenshotting.
Multiple Catchers per Project
Create separate request catchers per integration — one for Stripe, one for GitHub, one for Shopify — all in the same project.
Persistent History
Captured requests persist based on your project retention settings. Standard plan keeps 7 days of history.
Delete and Reset
Clear all captured requests for a catcher at any time for a clean debugging session.
Common Webhook Debugging Scenarios
Testing Stripe Payment Events
Stripe fires events like payment_intent.succeeded, customer.subscription.updated, and invoice.payment_failed. Capturing these in MockFlow lets you inspect the exact payload structure, see the Stripe-Signature header, and verify your signature validation logic before it touches production.
Debugging GitHub Webhooks
GitHub sends events like push, pull_request, and release to your webhook URL. Using MockFlow, you can point GitHub at your catcher, trigger events from the GitHub UI, and see the full payload before building your CI/CD handler.
Inspecting Third-Party SaaS Events
Services like Shopify, Clerk, Resend, Supabase, and Slack all send webhooks. When their documentation is unclear or their event payloads differ from what you expect, point them at a MockFlow catcher to see the real payload before writing any handler code.
Frontend Teams Without a Backend
If your backend is not ready, mock the webhook handler response in MockFlow while capturing real events. You can inspect what the provider sends and replay it to your backend the moment it goes live.
Webhook Debugger FAQ
What is a webhook debugger?
A webhook debugger is a tool that gives you a unique public URL to receive HTTP requests. Any request sent to that URL is captured and displayed in real time — including the method, headers, body, query parameters, and IP address. This lets you inspect exactly what a webhook provider sends before you write any handling code.
How do I debug a webhook with MockFlow?
Create a free MockFlow account, open a project, and create a Request Catcher. You get a unique public URL like https://api.mockflow.io/my-project--abc123/catch/xyz. Paste that URL into your webhook provider (Stripe, GitHub, Shopify, etc.) and trigger an event. MockFlow captures the full request and shows you every header, the parsed body, query string, and IP address.
Is MockFlow free to use as a webhook debugger?
Yes. The free Standard plan includes request catchers, live inspection, and replay. You can start without entering any payment information.
Can I debug Stripe webhooks with MockFlow?
Yes. Set your MockFlow Request Catcher URL as the webhook endpoint in the Stripe Dashboard or Stripe CLI. Every event Stripe sends will appear in the request inspector with full headers, including the Stripe-Signature header needed for signature verification.
Can I replay a captured webhook request?
Yes. After a request is captured, use the Replay button to re-send it to any target URL — including localhost. This is useful for testing your webhook handler without waiting for the provider to fire another event.
What is the difference between MockFlow and webhook.site?
Both capture webhook requests. MockFlow also gives you mock API endpoints, request replay to any target URL, configurable response bodies, per-project settings, and a persistent developer workspace. Webhook.site is a simpler inspection-only tool.