Build the request deliberately
Use GET, POST, PUT, PATCH, DELETE, HEAD or OPTIONS, then add only the headers and query rows you enable. Raw body, form URL encoded and multipart field modes cover common REST payloads.
Network Tools
| Enabled | Header | Value |
|---|
| Enabled | Key | Value |
|---|
| Enabled | Key | Value |
|---|
Send a request to see the response.
Valid JSON responses appear here.
Response headers appear here when the browser exposes them.
Network workflow
This API Test page helps developers, QA testers and support teams build a REST request without opening a full API workspace. Select a method, add headers, append query parameters, choose a body type and send the request from the browser. The response panel gives you the status code, timing, size, content type, exposed headers, raw body and a JSON preview when the payload is valid JSON. It is useful for quick endpoint checks, webhook debugging, local API experiments and comparing what the browser can actually reach.
Use GET, POST, PUT, PATCH, DELETE, HEAD or OPTIONS, then add only the headers and query rows you enable. Raw body, form URL encoded and multipart field modes cover common REST payloads.
The result view separates body, JSON preview and response headers, while the status strip shows HTTP status, elapsed time, byte size and the reported content type.
Because requests run through browser fetch, CORS, mixed-content rules, private network access and endpoint policies are part of the result instead of hidden behind a proxy.
Start with an absolute URL such as https://api.example.com/users. Use the Query tab for filters, page numbers or search terms so duplicate keys and encoded values are handled consistently.
For JSON requests, use Raw JSON/Text and keep the payload valid JSON. The tool can format the body before sending. Form and multipart modes build browser-native request bodies from enabled field rows.
A 2xx status means the server accepted the request, not that your business rule is correct. A browser failure can mean CORS, DNS, TLS, mixed content or a blocked private network request.
This is a browser-based request tester, so it does not bypass CORS, replace Postman collections, manage shared environments, store credentials, run scheduled monitoring or perform contract testing. Requests are sent only when you click Send Request. The page does not need a devbruh server to process your request, but the target API receives whatever URL, headers and body you send and may log them. Avoid production mutations unless you are sure the endpoint and method are safe.
Yes. Choose POST, PUT or PATCH, add headers, query parameters and a supported body type, then send the request from your browser.
This tool sends requests from the browser, so CORS, mixed-content rules, private network access and endpoint security policies can block a request that a desktop or server-side client can send.
The tool runs in your browser and does not require a devbruh server to process the request. The target API still receives your URL, headers and body, so avoid sending secrets to endpoints you do not trust.
Yes. The response panel shows status, timing, size, content type, response body, exposed response headers and a formatted JSON preview when the response body is valid JSON.
You can test reachable local endpoints when your browser, page protocol and endpoint CORS policy allow it. Browser security settings may block private network or mixed-content requests.
No. It is a lightweight browser request tester for quick checks. It does not provide collections, shared workspaces, saved environments, authentication vaults, automated monitoring or contract testing.