New
Webhook Tester
Get a private URL that captures incoming webhooks, inspect each request live, and verify its signature.
How it works
API Request Builder
Put together an HTTP request without fighting quoting and escaping. Add params, headers, auth and a body, send it straight from your browser, and copy it as cURL, JavaScript fetch, Python requests or HTTPie.
Import cURL
Tip: in your browser's dev tools, right-click a request → Copy → Copy as cURL.
Browsers don't let pages set some headers, such as User-Agent, Cookie and Host. They're kept in the generated code but left out when you click Send.
Credentials stay in this tab. They aren't saved with your draft.
Response
Send the request to see the response here. Requests go straight from your browser to the API, so the API has to allow browser requests (CORS). If it doesn't, copy the cURL command and run it in a terminal.
Headers
- 01
Choose the method and enter the URL, or start from an example or by importing a cURL command.
- 02
Add query params, headers, authentication and, for POST, PUT or PATCH, a body.
- 03
Click Send to see the status, timing, headers and formatted response.
- 04
Copy the request as cURL, fetch, Python or HTTPie to use it elsewhere.
About this tool
A quick REST client that writes the code for you
Testing an endpoint usually means switching between API docs, a terminal and your editor. This builder keeps the request in one form and writes the equivalent code as you type, so you can try a call, then paste exactly the same request into a script or your app. Paste a cURL command from documentation or your browser's dev tools and it's split back into method, URL, params, headers, auth and body.
Requests are sent directly from your browser to the API, never through our servers. That keeps tokens private, but it also means the API must allow browser requests (CORS), and browsers won't let a page set a few headers such as User-Agent or Cookie. Many public APIs allow it; for those that don't, the generated cURL command runs the same request from a terminal.
Params, headers, auth, body
Bearer, Basic and API-key auth; JSON, form and raw bodies; toggle any row on or off.
Code in four flavours
cURL, fetch, Python requests and HTTPie, updated as you type with correct quoting.
Import cURL
Paste a command from docs or dev tools and edit it in the form.
Private by design
Requests go straight from your browser to the API. Credentials are never saved with your draft.
FAQ
Frequently asked questions
Why does my request fail when it works with cURL?
Browsers enforce CORS: the API has to say it accepts requests from other websites. Server-side tools like cURL aren't restricted. If an API doesn't allow browser requests, copy the cURL command and run it in a terminal.
Do my requests or tokens go through Instant.tools?
No. Requests are sent directly from your browser to the API you enter. Tokens, passwords and API keys stay in the page and aren't saved with your draft.
Can I test webhooks with this?
Yes. Create a URL with the Webhook Tester, then send requests to it from here to see exactly what arrives.
Which headers can't be sent from a browser?
Browsers block pages from setting headers such as User-Agent, Cookie, Host, Origin, Referer and Content-Length. They still appear in the generated code, which you can run outside the browser.
Missing something?
Tell us the tool you wish existed.
Describe the job and the file types involved. The most requested tools get built first.