Responses
After you Send, the response area shows what came back from the server: status, timing, size, headers, and body.
Status and metadata
You will typically see:
- HTTP status code (e.g. 200, 404, 500)
- Time elapsed for the request
- Size of the response body
Use these to quickly judge success and performance.
Timing sparkline
Saved requests display a tiny sparkline chart in the sidebar showing the last 10 response times. The chart is color-coded so you can spot performance trends at a glance:
- Green -- fast responses under 300ms
- Yellow -- moderate responses under 1s
- Red -- slow responses over 1s
This makes it easy to notice when an endpoint starts degrading without opening any dashboards.
Body: Pretty, Raw, Preview
- Pretty -- Formatted view when the body is JSON or similar structured data.
- Raw -- Exact bytes as text (useful for debugging).
- Preview -- For HTML responses, a sandboxed preview renders the page safely.
Headers
The Headers tab displays all response headers. A count badge on the tab label shows the total number of headers at a glance so you can tell whether there are headers worth inspecting without switching tabs.
Search
Use Ctrl+F (Windows/Linux) or Cmd+F (macOS) to search inside the response body. This is helpful for finding specific keys or values in large JSON payloads or log-like output.
Cookies
If the server sends Set-Cookie, you can inspect cookies in the dedicated Cookies tab. Cookies can be stored and sent on later requests to matching domains. See History & cookies.
Copy
Copy the body or headers to the clipboard for use elsewhere.
Very large responses
If a response exceeds the configured size limit, Gud API may not render the full body inline in Pretty/Raw. You can still open it in an editor tab when offered. The limit is controlled by Settings > gudApi.responseBodyLimit (megabytes). See Settings.
Errors and non-2xx
Failed responses (4xx/5xx) still appear in the response viewer. Read the status code and body; many APIs return JSON error objects with details.