Rates TodayNIFTY25,800.6+2.01%SENSEX83,919.7+2.21%Gold 24K ₹11,261.39/g down37.39Silver ₹130.72/g down2.38
InsightforGeeks

API Request Tester (REST Client)

A light REST client in your browser. Enter an address, add query parameters, headers, authentication and a body, press Send, and read the status, timing, headers and formatted response. Paste a cURL command to fill the form, and copy any request as cURL, JavaScript fetch, Axios or Python. The request goes straight from your browser to the API and never passes through our server.

Requests are sent from your browser, not from our server. APIs must allow browser calls (CORS), and local APIs on localhost work.

How to use it

  1. Choose the method, enter the address, and press Send. Add query parameters, headers, authentication or a body in the tabs first if you need them.
  2. Read the status, time and size, then the formatted body. The Headers view shows the response headers your browser is allowed to see.
  3. Press “Import a cURL command” to paste a command, for example one copied from your browser's developer tools (Network tab, right-click, Copy as cURL).
  4. Open the Code tab to copy the same request as cURL, JavaScript fetch, Axios or Python.

Frequently asked questions

Why do I get “The request failed” for an API that works elsewhere?

A web page may only read the answer from another site if that site allows it with CORS headers (Access-Control-Allow-Origin). Many APIs do not, because they are meant to be called from servers. The browser then hides the reply and only reports a failure. Allow this website in your API's CORS settings, or use cURL or a desktop tool for APIs that block browsers. The browser's developer console (F12) names the exact CORS problem.

Can I test an API running on my own computer?

Yes. Addresses such as http://localhost:3000 work from this page, because browsers treat localhost as a safe place, as long as your API allows browser calls (CORS). Some browsers ask for permission to reach devices on your network. Other private addresses, such as 192.168.x.x, are often blocked for web pages.

Do my requests, tokens or passwords go through your server?

No. The request is sent by your browser directly to the API. We never see the address, headers, body or response. The history keeps only the method and address in your own browser, with values that look like keys or tokens blanked out, and you can clear it.

Why can I not set headers such as Cookie, Host or User-Agent?

Browsers do not let web pages set a small group of headers, including Cookie, Host, Origin, Referer and User-Agent, so they are ignored. The tool warns you when you add one. Use the generated cURL command in a terminal if you need them. Requests also never send your cookies to the API, so a login that depends on cookies will not carry over.

Which response headers are shown?

Only the headers the browser lets a web page read. Those are a few basic ones plus any the server lists in Access-Control-Expose-Headers. Headers such as Set-Cookie are never visible to a page.

What is not supported?

File uploads and multipart forms, WebSockets and streaming responses are not supported, and responses are shown up to 10 MB. For those, use cURL or a desktop tool such as Postman or Insomnia.

Related tools

These tools run entirely in your browser and are provided free, without warranty. Check important results before using them in production.