Webhook Tester

Create a temporary URL for debugging webhook integrations. Incoming requests are stored briefly so you can inspect the method, headers, query parameters, and body.

Your endpoint

Endpoint response

Configure what the webhook sender receives after the request is captured.

Webhook forwarding

Automatically send each incoming webhook to your server and log the response.

Only http/https on ports 80/443 are allowed. Private/reserved IPs and redirects are blocked.
Placeholders are supported: {{request_id}}, {{method}}, {{timestamp}}. Maximum delay is 10000 ms.
Sample request

                    
                

            


            

                

                    

                        

                            
Incoming requests

                            
No requests yet

                        

                        
                    

                    

                


                

                    
Select a request from the list to inspect details.

                

            


            

                
Webhook Tester helps debug incoming webhook requests from Stripe, GitHub, Telegram, CRMs, no-code platforms, and your own services. Copy the temporary URL, paste it into an integration, and see exactly what reaches the server.

                
The tool stores the latest requests for one endpoint: HTTP method, full URL, query string, IP, User-Agent, headers, and body. JSON payloads are displayed in a readable format, while large bodies are truncated to a safe limit.

                
The endpoint is intended for development and debugging. Do not send permanent secrets or production data: anyone with the tokenized URL can access the latest captured requests, and storage is only meant for short test sessions.

            

        

    


    

    

    
            

            
How to use it

            
    
                                    
  1. Press Create endpoint to get a unique URL like legost.in/utilities/webhook-tester/…/capture.
    2. 
                                    
  2. Put it into the settings of the service that should send webhooks: Stripe, GitHub, the Telegram Bot API, a CRM or your own application.
    3. 
                                    
  3. Send a test event. The whole request appears on the page: method, headers, query parameters, body (JSON is highlighted), IP and time.
    4. 
                                    
  4. Inspect as many requests as you need — the endpoint keeps the latest ones until it expires.
    5. 
                            

        

    
            

            
When it helps

            
    
                                    
  • Payment integration: see the real event structure before writing a handler.
    • 
                                    
  • Signature debugging: compare X-Signature or X-Hub-Signature headers with what your code expects.
    • 
                                    
  • No-code scenarios: confirm that Zapier, Make or n8n really sends a request and in what format.
    • 
                            

        

    
            

            
Frequently asked questions

                            

                    How long does a temporary URL live?
                    
A few hours from creation. For permanent webhook intake deploy your own endpoint.

                

                            

                    What does the endpoint reply to the sender?
                    
Status 200 with a short JSON body. That is enough for the service to consider delivery successful and not retry.

                

                            

                    Is it safe to send real data there?
                    
The tool is for debugging. Do not send production secrets: anyone with the tokenised link can see the latest requests.

                

                    

    








    

        

            
Related tools