Developer Tools
JSON FormatterBase64 Encoder / DecoderHTML Minifier & BeautifierMarkdown PreviewerRegex TesterAPI Request TesterView all 25

API Request Tester

Build, send, and inspect a real request — then export it as code in 7 languages.

Runs in your browserNo sign-up required
Equivalent Code
curl -X GET 'https://jsonplaceholder.typicode.com/todos/1'

This sends a real request directly from your browser. Some APIs block cross-origin browser requests (CORS) even though they work fine from a server or the command line — if a request fails for that reason, the generated cURL code above will still work.

Test It, Then Copy Working Code

Most API testers stop at showing a response. This one also generates the exact same request as ready-to-use code the moment it's built — cURL, JS fetch, Axios, Python, PHP, Go, or Ruby — so testing an endpoint and writing the code that calls it become the same step instead of two.

Useful for: frontend developers testing an endpoint before wiring up real code, backend developers verifying their own API, and QA engineers checking responses by hand.

How to Use This Tool

  1. 1Build the requestMethod, URL, headers, body, and an auth type (Bearer, API key, or Basic).
  2. 2Send itA real request goes out directly from your browser.
  3. 3Read the responseStatus code, response time, headers, and a pretty-printed body.
  4. 4Export as codeThe exact same request as cURL, JS fetch, Axios, Python, PHP, Go, or Ruby.

Good to Know

  • This sends a genuine request from your own browser — not through a server relay — which means some APIs will block it with a CORS error even though the same request works fine from a server, a mobile app, or the command line. That's a real limitation of any pure-browser API client, not a bug in this tool.
  • When a request is blocked by CORS, the generated cURL code below still works, since curl isn't subject to the browser's CORS restrictions at all.
  • Recent requests are saved to your browser's local storage so you can quickly re-run one without rebuilding it from scratch.
  • Response time is measured from just before the request is sent to just after the response body finishes downloading, giving a realistic (not just time-to-first-byte) figure.

Frequently Asked Questions

Why did my request fail with no useful error?

The most common cause is CORS — many APIs are intentionally configured to reject requests made directly from a browser on a different domain. The tool flags this possibility directly and offers the generated cURL code as a working alternative.

Is this a full Postman replacement?

For quick one-off requests and generating starter code, yes. For things Postman handles that a browser fundamentally can't (bypassing CORS, complex environment variables, automated test suites), a dedicated desktop client is still the better tool.

Are my API keys or tokens stored anywhere?

Only the method and URL are saved to your request history in local storage — headers, body, and auth values are not persisted, so a token typed into the Auth field is gone once you navigate away.

Is this free to use?

Yes, completely free, with no account and no limit on how many requests you send.