Every Detail of Every Request
MockFlow shows you the complete picture for every captured request.
Method & Path
GET, POST, PUT, PATCH, DELETE — exact method and path captured.
All Request Headers
Every header the caller sent, including custom and provider-specific ones.
Parsed JSON Body
JSON bodies are parsed and displayed in a readable tree with syntax highlighting.
Raw Body Text
The unmodified raw body string is always available for comparison.
Query Parameters
Query strings are parsed into key-value pairs for easy inspection.
IP Address & User Agent
See which client or service sent the request.
Timestamp & Status
When the request arrived and what response code was returned.
Replay History
Every time you replay a request, the target URL and result are stored for reference.
Custom Response Body
Control what MockFlow sends back — useful when the provider checks the response.
Send Your First Request in 30 Seconds
After creating a catcher, test it immediately with cURL, Postman, or any HTTP client.
# 1. Sign in to MockFlow and create a Request Catcher.
# You get a URL like:
# https://api.mockflow.io/my-project--abc/catch/xyz
# 2. Send any request to it:
curl -X POST https://api.mockflow.io/my-project--abc/catch/xyz \
-H "Content-Type: application/json" \
-H "X-Custom-Header: my-value" \
-d '{"user": "alice", "action": "signup"}'
# 3. MockFlow responds immediately:
# HTTP/1.1 200 OK
# { "ok": true, "caught": true }
# 4. Open the MockFlow inspector — the full request appears.Capture a Form POST
curl -X POST https://api.mockflow.io/my-project--abc/catch/xyz \ -H "Content-Type: application/x-www-form-urlencoded" \ -d "email=user@example.com&source=homepage" # MockFlow stores: # Method: POST # Content-Type: application/x-www-form-urlencoded # Raw body: email=user%40example.com&source=homepage
When to Use a Request Catcher
Before Your Backend Exists
You are building a frontend or integration but your backend server is not ready. Point the provider at MockFlow, collect real requests, and use replay to hit your backend the day it goes live.
Debugging Third-Party Integrations
A payment provider, CRM, or SaaS tool is sending you requests and something is wrong. Capture the real traffic in MockFlow to see exactly what headers, payloads, and content-types they send.
Testing Webhook Event Structures
Documentation is not always accurate. Capture real events from Stripe, GitHub, Shopify, or Clerk to verify the exact field names and data shapes before you write any parsing code.
Sharing Request Details with Your Team
Copy a captured request's JSON, headers, or cURL to share with a backend developer or file a bug report with a provider.
Request Catcher FAQ
What is a request catcher?
A request catcher is a tool that gives you a unique public URL. Every HTTP request sent to that URL — GET, POST, PUT, DELETE — is captured and made available for inspection. You can see the method, all request headers, the parsed body, query string, and IP address in real time.
How is a request catcher different from a webhook debugger?
They solve the same problem. A request catcher is the general term for any tool that captures incoming HTTP requests. A webhook debugger is usually focused on webhook events from SaaS providers. MockFlow does both: you can use the same catcher URL for webhooks, API callbacks, form submissions, or any HTTP source.
Can I use MockFlow to capture POST requests?
Yes. MockFlow captures all HTTP methods: GET, POST, PUT, PATCH, DELETE, and HEAD. For POST requests it parses the body as JSON (when Content-Type is application/json), stores it, and also keeps the raw body text.
Does MockFlow support form submissions and multipart data?
MockFlow captures the raw body and content-type for any request. JSON bodies are parsed and displayed in a structured tree. Other content types are shown as raw text.
How long are captured requests kept?
Retention depends on your plan and project settings. Standard plan keeps 7 days of request history by default. You can adjust the retention period in project settings.
Can I share a captured request with my team?
Team sharing is on the roadmap. Currently, each Request Catcher belongs to your account. You can export or copy request details manually.