Capture and Inspect Webhooks
Create a persistent request URL, point a webhook sender at it, and inspect the payload in the browser. Replay the request to a public staging endpoint, and keep mock APIs in the same project.
Comparing capture tools? Read the Webhook.site alternative guide.
What you can do with a request URL
The catcher URL stays on the project. A free account is required. The service sending the webhook does not need a MockFlow login.
Any common HTTP method
GET, POST, PUT, PATCH, DELETE, HEAD, and OPTIONS are captured on the same URL.
Headers and query string
Every header is stored. Query parameters are parsed. Sensitive headers can be masked.
JSON and raw body
Valid JSON is parsed. Other payloads, including form bodies, stay as raw text.
Request history
Captured requests stay on the catcher. Default retention is 7 days, adjustable to 24 hours or 30 days.
Replay to a public URL
Re-send a captured request to another public HTTP or HTTPS endpoint. Private hosts such as localhost are blocked.
JSON response body
Set the JSON body the catcher returns. The status is HTTP 200.
A capture workflow
- Create a request catcher and copy the URL.
- Paste that URL into the service that sends the webhook.
- Trigger an event and open the inspector.
- Review headers, query parameters, and the body.
- Replay the request to a public staging URL when the handler is ready.
The MockFlow Request Catcher page includes a cURL example you can send before a provider is connected.
Mock APIs in the same project
Incoming webhooks and outbound API calls usually show up in the same feature. Catch the webhook here, then use the mock API server for the responses your frontend calls. Mock endpoints support response profiles, status codes, headers, and delays. Those controls are separate from the catcher, which always replies with HTTP 200 and your JSON body.
FAQ
How do I capture a webhook in MockFlow?
Create a Request Catcher in a project, copy the public HTTPS URL, and point the sender at it. The method, headers, query string, JSON body, and raw body show up in the inspector. A free account is required for that public URL.
What can I inspect on a captured request?
You can inspect the HTTP method, path, headers, query parameters, JSON body when the payload is valid JSON, and the raw body. Form payloads are stored as raw text with their content type. Sensitive headers can be masked.
Can I replay a captured webhook?
Yes. Replay sends the captured request from MockFlow's servers to another public HTTP or HTTPS URL, such as a staging endpoint. You can edit the method, headers, and body first. Private hosts, including localhost, are blocked.
What response does the catcher send back?
The catcher returns a configurable JSON body with HTTP 200. Custom status codes, response headers, and delays are configured on mock API endpoints in the same project.
Can I mock APIs in the same project?
Yes. Mock API endpoints live next to request catchers. Each endpoint can have response profiles, status codes, headers, and delays for frontend and integration testing.
Where is the Webhook.site comparison?
The comparison guide is the article Best Webhook.site Alternative for Capturing and Inspecting Webhooks. This page is the product workflow: create a URL, capture the request, and inspect it.