Input
Preparing your workspace…
How to use
- Choose a method and endpoint; configure Params, Headers, Body and Auth.
- Select Send request and inspect the response.
- Copy or download response data, or export the request as cURL or Fetch.
Debugging a browser HTTP request
Use the request form to examine what an endpoint returns for a chosen method, URL and set of request fields. Sample and cURL import prepare the form without sending it.
The browser is the client. Requests go directly to the selected endpoint, so both the result and any access restrictions reflect that browser context rather than a server-side proxy.
Preparing and sending
Sample fills an example request, and cURL import maps supported options into visible fields. Review them before selecting Send request or pressing Enter in the request form.
Enabled parameters and headers are applied to the URL and request. Browser-managed headers cannot be overridden, and GET/HEAD requests cannot carry a body here.
GET https://httpbin.org/anything?source=devtoolsyHTTP 200
Response headers, elapsed time and bodyExample data only. Values, authentication and endpoint behavior must be checked in your own context.
Reading browser-visible responses
CORS and credential rules determine which response data the browser exposes. Only exposed headers can be shown; HTTP errors such as 401 or 500 are responses, while network/CORS failures are reported separately.
Exporting requests and responses
Export request generates cURL or Fetch code without sending it. Response Download saves received bytes; Copy exports text, optionally formatted as JSON. Truncated responses cannot be exported as complete results. Review exported authentication values before sharing request code.
Local tools accept up to 1 MiB, URLs up to 64 KiB, and have a 5-second processing limit. API requests support 100 headers and 100 parameter rows, a 1–120 second timeout and up to 5 MiB of received response data. Long text previews are abbreviated. Requests go directly to your chosen endpoint; CORS and browser policy apply.
Frequently asked questions
Why does a request work in cURL but fail here?
The browser may require a successful CORS preflight, access-control headers and a compatible credential policy. A network error does not establish that the endpoint received nothing.
Where do my tokens and request data go?
Selecting Send transmits the configured URL, allowed headers, authentication and body directly to the endpoint. DevToolsy does not proxy the request or save a request history.
Does Sample or cURL import send automatically?
No. Both fill the form. Sending requires the request form’s submit action, such as Send request or Enter in its URL field.
Can Cancel undo an operation on the server?
No. It stops waiting or reading in the browser. The endpoint may already have received and acted on the request.
Why can some response headers or bodies be unavailable?
Browser response policies can hide headers or block an opaque response. Responses are also capped at 5 MiB; a truncated result is marked and cannot be exported as a complete response.