Skip to main content
New insight available. View changelog →
Start Tier 1

Web & APIs · SupportRoadmap Docs

HTTP requests and responses for support

An HTTP exchange is a request from a client (browser, mobile app, or integration) and a response from a server. For support, the useful parts are usually the method and URL, status code, key headers, and whether the response body shows a product error, auth failure, or empty result.

By Tom Ulman · Published · Last reviewed

What you are looking at

Every browser or API call is a request (what the client asked for) and a response (what the server returned). In DevTools’ Network panel, each row is one exchange. Support does not need to design HTTP—you need to read enough of the exchange to describe the failure accurately.

Parts that matter on tickets

  • Method and URL — GET, POST, PUT, PATCH, DELETE, plus the path and query string (IDs, environment hints).
  • Status code — see HTTP status codes for software support.
  • Request headers — especially Authorization, cookies, content type, and tenant or org headers your product uses.
  • Response body — JSON error messages, empty arrays, or HTML error pages often explain more than the UI toast.
  • Timing — long waits can be network, cold starts, or a slow dependency.

Support example

A customer says “export never finishes.” Network shows POST /exports returning 202 quickly, then GET /exports/123 polling with 200 and a JSON body like { "status": "processing" } for minutes. The ticket should describe the polling pattern and last status—not only “button does nothing.”

Caveats

  • Not every important failure is the first red row; look for the request that owns the customer action.
  • Bodies and headers can contain secrets—redact before sharing (see HAR guidance).
  • Mobile apps may not expose DevTools; you may need product logs or a HAR from a web equivalent.

Related practice

Capture a full session with HAR files, then walk a failing call in the API troubleshooting guide.

Related concepts

Primary sources

Prefer an ordered path? Open the related roadmap skill and work through it with the curated resources.

Learn this in order