HTTP Request Tester

Postman is overkill when you just want to verify a webhook or poke a public API. Paste a URL, pick GET/POST/PUT/PATCH/DELETE, add headers and a body, and this tester fires the request and shows the status code, response headers, body and total response time.

How to send a test request

  1. 1

    Pick method and URL

    GET, POST, PUT, PATCH, DELETE or HEAD, plus any URL reachable from our server.

  2. 2

    Add headers

    Authorization, Content-Type, custom headers: one per line, as many as you need.

  3. 3

    Set the body

    Raw text, JSON, form-urlencoded or multipart. The body is only sent with the methods that support it (POST, PUT, PATCH, DELETE).

  4. 4

    Send and inspect

    Status code, total response time, headers and body all show side by side.

What the tester returns

Every response is presented as four useful parts.

1. Status code

HTTP 200, the numeric status code of the response. Any status in the 4xx or 5xx range is highlighted for quick diagnosis.

2. Response time

Total time from request start to the full response, measured on our server in milliseconds. A response above 500 ms on a same-region API is a red flag, usually a slow backend or a missing index.

3. Response headers

All response headers are listed in order, with the exact values the server returned.

4. Body

  • The body is shown exactly as the server returned it, without reformatting.
  • JSON and XML are easy to read in the monospace output area.
  • Binary responses (images, PDFs) appear as raw data; for those, curl or httpie is a better fit.

Tips

  • Use POST with JSON when testing a REST API: set Content-Type: application/json and paste the body as a JSON object.
  • For OAuth-protected endpoints, paste the Authorization: Bearer <token> header directly.
  • Requests run from our server, so browser CORS rules do not apply. Use this to test endpoints your browser would block.

Frequently Asked Questions

The tester is built for API-sized payloads, not bulk transfer. For very large uploads (video, binary archives), a purpose-built tool like curl or httpie is a better fit; this tester is meant for testing APIs, not moving large files.

Yes. Paste the cookie value into a Cookie header. The tester does not share your browser cookies with the target by default, so you control exactly what is sent.

The request is executed from the tool’s server (to bypass browser CORS limits). Nothing is persisted beyond the single response you see; the request is not stored or logged.

No, this tester is scoped to plain HTTP request-response. For WebSocket testing, use a dedicated WS client that speaks the full upgrade handshake and frame protocol.

Related Tools

Tool available in other languages