REST Client
NewMake HTTP requests directly from your browser — set method, URL, headers, and body, then inspect the response.
Browser API client
REST Client
Make HTTP requests directly from your browser — set method, URL, headers, and body, then inspect the response.
Requests run in your browser, so the target API must allow CORS.
Response
Frequently Asked Questions
Why does the request fail in the browser even though the same call works in curl or Postman?
Because this tool uses fetch in your browser, the target API has to allow the request with CORS headers. The component even warns about this up front, and failed cross-origin requests fall back to a CORS/network error message.
Can I send auth headers or other custom headers?
Yes. You can add any headers manually, including Authorization, Accept, or Content-Type. There isn't a separate auth helper, but the header rows are flexible.
Will it pretty-print JSON responses?
Yes. If the response Content-Type includes 'json' or the body looks like it starts with { or [, the tool tries to parse and reformat it with indentation. If parsing fails, it shows the raw text instead.
Why do the response headers look incomplete?
The tool can only display headers the browser exposes to JavaScript. If CORS doesn't expose them, you'll see '(No response headers exposed by the browser)' even though the server may have sent more.
Can I send a body with any HTTP method?
No. The body field is only enabled for POST, PUT, and PATCH, and only those methods include options.body in the fetch call. GET and DELETE requests are sent without a request body here.