↑↓ to move · Enter to open · Esc to close

HTTP Request Tester

Send a POST, PUT, PATCH, DELETE, or any other method with this HTTP request tester. Set query parameters, headers, and a JSON, form, or raw body, then read the reply and copy the same request as a cURL command.

This request runs on our server. The address, headers, and body you enter are used only for this request and are not stored.
Built and reviewed by · Updated

Request

Tick the box to show you are not a robot, then press Send.

Up to 100 KB. JSON is checked before it is sent. Form fields are URL-encoded.

Response

The response shows up here

Tick the robot check and press Send. The status, body, headers, and any redirects land in this pane.

  • Status, time, and size
  • JSON as a tree, or the raw text
  • Response headers and redirect hops

cURL command

 

                
The command repeats the request from your own computer, with your own User-Agent.

            

        

    


    

            
Public addresses on ports 80 and 443. The User-Agent names Utilza and stays fixed.
            
            Ctrl + Enter sends

    

                                                
        

                    

            
How to use the HTTP Request Tester

        
  1. Pick the method and enter the URL.
  2. Add query parameters as name and value rows; they are encoded and appended for you.
  3. Add headers, then choose the body type. JSON is checked before it is sent, form fields are URL-encoded, and raw text goes with the Content-Type you give it.
  4. Decide whether redirects should be followed.
  5. Tick the robot check and press Send. The cURL box below updates as you edit, so you can repeat the request from a terminal.



                    

            
How it works

        
The request is built on our server from the parts you enter and sent with a User-Agent that names Utilza, so the receiving side can tell where it came from. Host, Content-Length, Transfer-Encoding, Connection, and Proxy headers are set by the server and cannot be overridden, and a header value with a line break is refused. That stops one request from being turned into two.
Redirects follow browser rules. After a 303, or a 301 or 302 that answered a POST, the next request is a GET without a body. A 307 or 308 repeats the original method and body. When a redirect moves to a different host, Authorization and Cookie headers are not passed on, and the result says so.
The cURL command is written in your browser by the same code as the cURL Command Builder, quoted for the shell you pick.



                    

            
Examples

        
The form opens with a POST to https://jsonplaceholder.typicode.com/posts and the JSON body {"title":"Test","completed":false}. That service echoes the post back with status 201 and a new id, without saving anything, which makes it a safe first target.
The matching Bash command is:
curl 'https://jsonplaceholder.typicode.com/posts' \
  -H 'Accept: application/json' \
  -H 'Content-Type: application/json' \
  --data-raw '{"title":"Test","completed":false}' \
  -L
Switching the method to GET drops the body, and a note in the result says it was left out.



                    

            
Limitations

        
  • Public addresses on ports 80 and 443 only. A development server on localhost or a custom port is out of reach; run the cURL command on your own machine for those.
  • No file uploads (multipart forms), and the body is capped at 100 KB.
  • The User-Agent cannot be changed.
  • Each request is sent once. There is no collection, history, or environment variables as in a desktop API client.



            

                                    

        
Frequently asked questions

        

                            

                    Why is my header refused?

                    
Headers that control the connection, such as Host or Content-Length, are set by our server, and the User-Agent always names Utilza. A value with a line break is also refused.

                

                            

                    Do you keep the requests I send?

                    
No. The URL, headers, and body are used for that one request and are not written to a database or a log.

                

                            

                    Why did my POST turn into a GET?

                    
The server answered with a redirect such as 301, 302, or 303, and browsers switch to GET when they follow it. Untick Follow redirects to see the first answer, or send the request to the final address.

                

                            

                    Can I test webhooks with this?

                    
Yes, if the receiving endpoint is public. Paste the payload your provider sends as a JSON body, add its signature header, and compare the response with what your handler should return.

                

                    

    

        

        

            
            
Often used together with HTTP Request Tester.

        

        
    
                            
  • 
    

    
    cURL Command Builder
    
    
            
    Builds copy-ready cURL commands with headers, auth, and a body, quoted for your shell.
    
    
    

    • 
                            
  • 
    

    
    API Response Viewer
    
    
            
    GET any public API endpoint and read its JSON as a tree, with status, time, and headers.
    
    
    

    • 
                            
  • 
    

    
    HTTP Header Parser
    
    
            
    Header table with meanings, expanded Cache-Control, cookies, CSP, and Accept values, plus problem lines.
    
    
    

    •