HTTPfy

HTTP Request Tester

Send requests with custom methods, headers and bodies.

Protocol
Method
HTTP Request Tester Ready

About HTTP Request Tester

HTTP Request Tester: Send Custom Requests to Any API or URL

The HTTP Request Tester sends a request from our server to a public URL and shows you the response status, headers and body. Use it to check an API endpoint, try a webhook receiver, or see how a site answers different methods and user agents without installing curl or Postman.

What You Can Set

  • Method: GET, HEAD, POST, PUT, DELETE, PATCH or OPTIONS.
  • Protocol: http or https. You can also type the full URL with its scheme.
  • User agent: our default, Chrome, Firefox or Safari presets, or your own string.
  • Headers, cookies and query parameters: one per line in key=value form, for example Authorization=Bearer abc123. The tool adds query parameters to the URL as written, so URL-encode values that contain spaces or &.
  • Body: JSON (sent with Content-Type: application/json) or plain text (sent as text/plain).

What You Get Back

  • The final status code and all response headers.
  • The start of the body: up to 1,500 characters of JSON, pretty-printed, or the first 500 characters of HTML and other types.

The tool follows up to 5 redirects. If a redirect leaves the original site, it drops your Authorization header and cookies so they don't leak to another host. Requests time out after 30 seconds.

Things to Know

  • Public addresses only: the tool blocks private and internal ranges such as 10.0.0.0/8, 192.168.0.0/16 and localhost, so you can't reach services on your own network.
  • Extra headers: every request carries x-server-name: httpfy.io and x-requester-ip-address with your IP address, so the target server can see who sent it.
  • Secrets: don't paste production API keys or session cookies. Use test credentials and rotate any key you've shared with an online tool.

Common Status Codes

  • 200, 201, 204: success. 201 means the server created something, and 204 means success with no body.
  • 301, 302, 307, 308: redirects. 307 and 308 keep the method and body; browsers turn a POST into a GET on 301 and 302.
  • 400, 401, 403, 404, 405, 429: bad request, missing credentials, forbidden, not found, method not allowed, rate limited.
  • 500, 502, 503, 504: server-side errors. 502 and 504 often come from a proxy or load balancer in front of the app.

To see what your own client or webhook sender transmits, use the webhook and HTTP request inspector.