Inspecting Requests

Open a captured request

Open the endpoint workspace with valid guest management access or the owning account. Select a row to inspect it. New traffic appears in the list while your selection stays available.

Use Overview to compare method, path, receive timestamp and response status with the sender’s delivery record. If you need a known example, send the synthetic order request.

Read the body

Open Body. JSON has formatted, tree and raw views for exploring structure and text. Invalid JSON remains inspectable as text; capture does not depend on successful JSON parsing.

{
  "event": "order.created",
  "order": {
    "id": "order_demo_001",
    "status": "created"
  }
}

If UTF-8 decoding fails, the inspector displays base64. A binary Content-Type alone does not force base64 display; original bytes are preserved separately.

Headers and query parameters

Headers shows captured header names and values; casing may differ from the sender. Search for x-demo-event from Quickstart. Do not paste sensitive header values into reports.

Query shows URL parameters, including repeated keys. For ?tag=first&tag=second, expect both values rather than a single merged field.

Metadata and Raw

Overview includes receive time, size, source IP and response metadata. Source IP is best effort and may represent a network intermediary.

Raw reconstructs a readable request from captured fields. It is not a packet trace: original wire formatting, header casing and protocol details are not guaranteed.

Search and filters

Search matches substrings in loaded request paths, bodies and headers. Use path:/orders to restrict the match to paths or header:x-demo-event for headers. Method and status filters further narrow the list. Clear all filters when diagnosing a missing delivery.

The workspace initially loads the latest 100 requests. There is no older-page list navigation. A selected older request may be loaded independently by its known ID; search does not query every retained record.

Real-time updates

Watch the connection banner. If updates stop, use Reconnect or reload. Reconnection refreshes the latest saved history, not every historical record.

Saved captures are the source of truth. The receiver can keep capturing while the application backend is unavailable; retry loading history after connectivity returns. Filters may still hide saved requests.

Download and export

Use Download JSON for the selected request or Export NDJSON for records matching your filters across accessible retained history, beyond the loaded list. Endpoint access and retention rules still apply.

Downloads include schemaVersion and original body bytes in bodyBase64. The configured response is a historical configuration snapshot, not proof of bytes received by the sender; older records may have a null snapshot.

Exports have size and time bounds. If export fails, narrow your filters and retry. This is not unbounded archival or a way to recover expired/deleted data. Files contain unredacted captures: store and share them carefully.