cURL Runner

Paste any curl command, hit Run Request, and see the response. Works with Postman’s “Copy as cURL”, Swagger, and terminal exports.

Server mode runs the request on this site’s server (like Postman). Your auth headers are not stored — only forwarded for the request.

What this tool does

cURL Runner sends HTTP requests from your browser through our server proxy — test GET, POST, PUT, PATCH, DELETE with custom headers and body, then inspect status, headers, and response body.

Use it to debug APIs, webhooks, and REST endpoints without opening a terminal.

Why use cURL Runner

  • Quick API testing without installing Postman or curl locally.
  • Shareable workflow — copy request settings from docs and run immediately.
  • Inspect response headers and JSON/XML bodies in one view.
  • Helpful on locked-down work laptops where CLI tools are restricted.
  • Free for endpoints you are allowed to test.

How it works

Enter a URL, pick the HTTP method, add headers and body if needed, then run the request. Results show status code, timing, headers, and body.

  1. Paste the API endpoint URL.
  2. Select method (GET, POST, etc.).
  3. Add Authorization or Content-Type headers if required.
  4. Paste JSON or form body for POST/PUT requests.
  5. Run and review the response — copy or troubleshoot from there.

Step-by-step instructions

Test a JSON POST endpoint

  1. Set method to POST.
  2. Add header: Content-Type: application/json.
  3. Paste the JSON body from your API docs.
  4. Run and verify status 200 and expected fields.

Example

Scenario: A developer verifies a staging webhook before go-live.

  1. Pastes the webhook URL into cURL Runner.
  2. Sets POST with a sample JSON payload.
  3. Confirms 200 OK and correct response body.
  4. Fixes server config before production deploy.

FAQs

Can I test any URL?
Only use URLs you own or have permission to test. Do not probe third-party systems without authorization.
Are credentials stored?
No. Requests run in real time and are not saved on disk.
CORS errors?
The proxy runs the request server-side so browser CORS limits do not apply the same way as fetch from DevTools.
Request size limits?
Large responses may be truncated to protect server resources — check the status message on the page.

Related tools