← Back to Overview

HTTP CLIENT

Response Viewer

Everything about reading API responses — status codes, timing, body views, headers, cookies, the actual request sent, test results, and schema extraction.

Response viewer showing status, time, body

Status Bar

The top of the response area shows three key metrics at a glance:

200 OK

Status code + text, color-coded

45 ms

Total response time (clickable)

1.2 KB

Response body size

Status code colors:

2xx — Success 3xx — Redirect 4xx — Client Error 5xx — Server Error

Timing Breakdown

Click the response time to expand a detailed breakdown of each network phase:

PhaseDescription
DNS LookupDomain name resolution
TCP ConnectTCP handshake to server
TLS HandshakeSSL/TLS negotiation (HTTPS only)
TTFBTime to first byte — server processing time
DownloadResponse body transfer
Timing breakdown showing DNS, TCP, TLS, TTFB, and download phases

Click the time value to toggle the breakdown — useful for diagnosing slow responses

Body Tab

Three view modes for the response body, selected via sub-tabs:

Pretty

Syntax-highlighted CodeMirror editor (read-only). Supports 9 language modes: JSON, HTML, XML, CSS, JavaScript, YAML, GraphQL, TypeScript, plain text. Ctrl+F search with scrollbar match highlights. A-/A+ zoom.

Raw

Plain unformatted text. Useful for non-JSON responses or when you need to see exact whitespace and encoding.

Tree

Interactive collapsible JSON tree. Click to expand/collapse objects and arrays. Shows key counts. Best for exploring deeply nested responses.

Toolbar actions: Copy body to clipboard, Copy Schema (generates TypeScript types), Word Wrap toggle, and the history dropdown (browse previous responses for the same URL).

Headers Tab

Displays all response headers in a two-column table (name → value). Click any value to copy it to clipboard.

Headers are shown as returned by the server — case is preserved. Common headers like content-type, x-request-id, and set-cookie appear here.

Cookies Tab

Parsed cookies from Set-Cookie response headers. Shows all cookie fields:

name value domain path expires httpOnly secure sameSite

Cookies are automatically saved to the cookie jar (if enabled) and sent with future requests to the same domain.

Actual Request Tab

Inspect exactly what was sent over the wire — after all variable interpolation, auth injection, cookie attachment, and pre-request script execution.

Formatted view — Structured display: method, full URL, all headers, body
Raw HTTP view — Traditional HTTP message format (request line + headers + blank line + body)
Protocol — Shows HTTP/1.1 or HTTP/2
Certificates — Shows which TLS certs were used (or "System Trust Store")
Actual Request tab showing resolved URL, headers, and body

Invaluable for debugging — see the resolved {{variables}}, injected auth headers, and final body

Test Results Tab

Appears when the request has GUI test rules or test scripts. Shows pass/fail for each assertion:

Passed — Green check with the rule label (e.g. "status equals 200")
Failed — Red cross with expected vs actual values (e.g. "expected 200, got 404")

Also shows Set Variable results — which variables were extracted and whether they were saved to the environment. Plus script console output from console.log() in test scripts.

Schema Extraction

Click Copy Schema in the body toolbar to generate TypeScript-style type definitions from the response.

FormatHow it works
JSONInfers types recursively. Arrays merge up to 50 elements (unions for mixed types, optional keys marked ?)
YAMLIndent-based tree parsing, generates interfaces from structure
XMLStack-based tag parser, repeated children typed as arrays
GraphQL / TSExtracts existing type/interface/enum blocks directly

Example output from a JSON response:

interface Response {
  userId: number;
  id: number;
  title: string;
  body: string;
}

History Dropdown

The response toolbar includes a history dropdown that shows previous responses for the same URL. Click any entry to view that historical response without re-sending.

Shows timestamp, status code, and response time for each entry
Delete individual entries or clear all history for that URL
Useful for comparing responses over time or after code changes

Next

Ko-fi