What is captured for each request?

Method, full path and query string (parsed into a table), every header in original order, the client IP, the body up to 256 KB (gzip, deflate and brotli are decoded automatically, binary bodies are kept as base64) and the response the bin sent back.

Can I control what the bin responds with?

Yes. Under Response settings choose the status code, up to 20 headers, a body up to 64 KB, a delay up to 10 seconds and whether CORS headers are added. Presets cover 200 JSON, 204, 500, a 302 redirect and a slow 5 s response. Changes apply to the next request.

Does it work with signed webhooks like Stripe or GitHub?

Yes. The raw body and signature headers are preserved exactly as sent, so you can verify signatures offline. Use Copy as cURL or Replay to forward the identical request to your local tunnel or staging server.

Why does the page say the bin expired?

Either an hour passed without a request (or the 3-hour lifetime ended), the relay restarted, or you created a new bin from another tab. Click Create new bin to get a fresh URL; captured requests are not recoverable once a bin is gone.

Request Bin

Create a private endpoint in one click and point any webhook, callback, pixel or API client at it. Every request appears instantly over a live stream with method, path, query, headers, decoded body (JSON highlighted, forms as tables, gzip/deflate/brotli decoded) and the raw HTTP/1.1 wire format. Configure the response your bin sends (status, headers, body, delay, CORS), replay captured requests to your own server, copy them as cURL, or open them in the HTTP Request Tester. Bins keep the last 100 requests for an hour of inactivity (three hours at most) and then self-destruct.

Live endpoint via the FizzKit relay — captured data auto-deletes after 1 h idle

Your endpointConnecting…

Creating your private endpoint…

Any method, path or query under this URL is captured and answered with the response configured below. Keeps the last 100 requests for 60 min of inactivity (3 h max) · bodies up to 256 KB (gzip, deflate and brotli are decoded).

Requests

Req / min

Last seen

—

Unique IPs

Methods

—

Stored

0 B

HTTP Request Tester

Send GET, POST, PUT and other requests to any public URL and inspect status, headers, body, redirects and timing.

HTTP Status Codes

Searchable reference for every HTTP status code.

JSON Formatter

Beautify, minify, sort, query and repair JSON with a tree view and copy-as code export.

URL Parser & Query Editor

Break any URL into parts, edit query params live, unwrap nested redirect URLs, decode ad macros, build UTMs and follow redirects.

WebSocket Tester

Connect to any ws:// or wss:// endpoint, send text/JSON/binary frames, measure RTT, and debug Socket.IO, STOMP, graphql-ws and MQTT handshakes.

How to use Request Bin

1Copy the endpoint URL (or scan the QR code) and paste it wherever a webhook or callback URL is expected.
2Send a request — use the Send a test request button or the cURL, JavaScript and Python snippets to try it immediately.
3Click a request in the list to inspect its headers, decoded body, query parameters, raw wire format and the response the bin returned.
4Adjust the Response settings to simulate errors, redirects or slow endpoints, then replay any captured request to your own server.

About Request Bin

Request Bin is part of FizzKit — a collection of focused developer and ad-tech tools. This tool gives you a live endpoint on the FizzKit relay; captured requests live in memory only and are deleted automatically after 60 minutes of inactivity (3 hours at most).

Frequently asked questions

A bin expires 60 minutes after its last request (3 hours at most) and keeps at most 100 requests (1 MB). Only the browser that created it holds the owner token, which is stored in local storage; the capture URL itself is public, so anyone who knows it can send to it.

Related tools