GET 1 credit

Captured Request Inspector

List and inspect captured HTTP requests in a bin

How to Use

  1. 1. Provide the `bin_id` in the URL path to specify which bin to inspect.
  2. 2. Optionally set `limit` (1–200, default 50) and `offset` (default 0) query parameters for pagination.
  3. 3. Review the returned summaries — each includes the HTTP method, path, source IP, timestamp, and content length.
  4. 4. To see full details (headers, body, query string), fetch a specific request by its `request_id`.

About this Tool

The Captured Request Inspector lets you browse all HTTP requests that have been sent to a bin's catch URL. It returns a paginated list of request summaries sorted newest-first, and you can drill into any individual request to see the full headers, body, query string, and content type.

Use this endpoint after configuring a third-party service to send callbacks to your bin. You can verify that requests are arriving, check their structure, and debug any payload issues.

For full request detail including headers and body, use `GET /v1/bins/{bin_id}/requests/{request_id}`.

Use Cases

Webhook payload verification

Confirm the structure and frequency of incoming webhook calls

Integration debugging

Check which HTTP methods and headers a third-party service actually sends

Request timeline analysis

Review the sequence and timing of captured requests

Automated testing validation

Verify your test suite generates the expected HTTP calls

FAQ

Are requests returned in chronological order? expand_more
Requests are returned newest-first (reverse chronological). The most recently captured request appears at the top of the list.
How do I see the full request body and headers? expand_more
The list endpoint returns summaries only. To see full details including headers, body, query string, and content type, use `GET /v1/bins/{bin_id}/requests/{request_id}` with the specific request ID.
What happens if I request a deleted or expired bin? expand_more
You'll receive a 404 error with the message "Bin not found or expired". Bins and all their captured requests are permanently removed after expiration or deletion.
Try Captured Request Inspector →