Skip to content

Reading a response

A response appears below its request. In a file tab, it’s the response of whatever ran last, labelled with its request; click the label to go to that request.

The bar above a response shows the status, how long it took and the body’s size. Hover over the size to see how big it was as received, when the server compressed it. If the request has tests, the bar shows how many passed.

Tab Shows
Body The body, formatted.
Headers The response headers.
Cookies The cookies the response set, and the cookies the request sent.
Token Any JWT the request sent or the response returned, decoded.
History Earlier responses to this request, to compare with. See History and comparing.
Tests Each test and whether it passed.
Timing Where the time went, and the connection: HTTP and TLS versions and the server’s certificate.
Variables The {{variables}} that went into the request, and where each value came from.
Sent request Exactly what was sent, with variables filled in and any redirects followed.
Console Output from the request’s scripts.

Some tabs only appear when they apply. Debugging explains the Timing, Token, Cookies and Sent request tabs in detail.

A JSON body has a filter box. Type a JSONPath to show just what matches:

Filter Shows
$.items[*].id Every item’s id.
$..name Every name, at any depth.
$.data[0] The first element of data.

Right-click a value for Assert …, which adds a test, and Copy path, which copies its JSONPath.

  • An image (PNG, JPEG, GIF, BMP, WebP or ICO) is shown as a picture, with its size and type.
  • Other binary bodies, such as PDFs, archives and downloads, are described rather than shown as garbled text.
  • The copy button copies whatever tab is showing: the body, headers, sent request, tests or console. You can also select text in the body and copy it.
  • Save body…, under the download button by Copy, saves the body exactly as received, named from the request and its content type.
  • Save as HAR saves the request and response as a HAR file. See Debugging.
  • To save responses every time a request is sent, add >> ./out/result.json after it. See .http syntax.

Values that look like secrets show as ••• until you press the eye button beside them: bearer tokens and passwords on the Auth tab, headers and parameters with credential-like names (Authorization, X-Api-Key, Cookie, and names containing token, secret, password or session), and environment values with such names. Copying a masked response header copies it masked.

Clear, next to Snapshot, removes a request’s response and its history. The .http file and any snapshot stay as they are.