Inspecting a request
Select a row and the detail panel opens on the right: a request pane and a response pane, each with Summary, Headers, Body and Raw. Click the URL or any field to copy it.
Actions
The action row acts on the selected request:
| Action | Does |
|---|---|
| Repeat (⌘R) | Send the same request again. |
| Edit & send | Open it in the API client to change and resend. |
| Breakpoint (⌘B) | Pause the next matching request or response to edit by hand. |
| cURL (⇧⌘C) | Copy as a curl command (or redacted). |
| Highlight | Color the row, or set auto-color rules. |
| Comment | Attach a note, searchable with comment:. |
| More (…) | Code snippet, Mock this response (Map Local), add to Compare, pin host, edit record, open in a new window, show URL as a QR code, delete. |
Body viewers
The body shows in the right form for its type, with a tab bar to switch:
- JSON — Text, a collapsible Tree, or a JSONPath query box.
- HTML / JS / CSS — Pretty-printed, with Render to open HTML in a browser.
- Images — Preview.
- SSE — Events, or the Raw stream.
- Any body — Hex, and Wire for the encoded bytes.
Body tools: Find (⌘F), Wrap, Copy body, and Save body to a file.
The Summary panel
Summary collects what elcapture worked out about the request. Sections appear when they apply:
| Section | Shows |
|---|---|
| AI model call | Model, token counts and estimated cost — see AI model calls. |
| Anti-bot / WAF | Detected protection: Cloudflare, DataDome, PerimeterX/HUMAN, Akamai, Imperva, Turnstile, hCaptcha, reCAPTCHA. |
| Timing | Connect, TLS, Waiting and Download phases; Total and Time to first byte; a Failed stage if it errored. |
| Decoded request | GraphQL operation, query and variables; query parameters; multipart parts; cookies; Authorization. |
| Connection | Server IP and port; connection reused or new; upstream proxy; TLS version and cipher; ALPN; client certificate; JA3 and JA4 fingerprints. |
| Server certificate | Leaf and issuer subjects, who issued it, valid-until, and SAN names. |
| gRPC | Method, status code and message for gRPC calls. |
| Client | App, HTTP version, request and response body sizes, and which rules were applied. |
Editing at a breakpoint
When a breakpoint pauses a request or response, the panel shows Paused at… and lets you edit the first line, the headers and the body (a structured editor, or raw). Then continue with Execute, answer instantly with Reply 429 or Reply 503, restore the Original, Abort the connection, or Execute all queued breakpoints. An auto-continue timer (off, 30s, 60s, 3m) keeps you from blocking forever.