Captured requests appear in the main table. Use pins and filters to focus on the traffic that matters.
Each row is a single HTTP transaction (or WebSocket upgrade). Columns typically include client/app name, method, path/URL, status, status code, and time. Selecting a row opens the detail pane with request and response tabs (headers, body, raw, cURL).
Detail vs list: The list may use a compact JSON payload for performance; the detail view resolves the full stored entry (including complete headers and bodies) when you select a row. Copy URL / cURL from the context menu also prefers the full entry when available.
Pinned hosts (or patterns) let you focus on APIs you care about. The sidebar can switch between All traffic and Pinned views depending on your workflow.
Filters (such as All, REST API, GraphQL, Incomplete, Errors) are applied on the Swift side to narrow what you see—useful for noisy captures.
Right‑click a row to copy the request URL or a cURL command. cURL is built from the full captured request when the store still has the entry, so replay matches what the proxy saw.
Authorization, cookies, or API tokens. Paste carefully—treat exports like passwords.Some builds offer repeating a request (re‑fire through the proxy or client stack). Results appear as new traffic rows.