How this works: Requests are sent directly from your browser, so the endpoint must allow cross-origin requests (CORS). Many public webhook URLs (Slack, Discord, etc.) and private/local servers block browser calls — those will report a CORS/network error even though the request may have succeeded server-side. Because of CORS, only a limited set of response headers may be visible. The generated cURL command always works from a terminal with no such limits. Nothing you enter leaves your browser except the request itself.

Request Builder

Request URL

Body

Headers

Query Params

Auth

Size: 0 bytes

Variables are replaced when the request is sent. Body is ignored for GET and HEAD.

Authentication Type

cURL Command

Response

📡

Send a request to see the response

How to Use This Tool

Enter the webhook URL — Paste the endpoint URL you want to send a request to
Choose HTTP method — Select GET, POST, PUT, PATCH, or DELETE from the method dropdown
Configure the request — Add custom headers, authentication (Basic, Bearer, API Key), query parameters, and a request body as needed
Send and inspect — Click "Send Request" to fire the webhook and review the response status, headers, and body
Use templates — Load pre-built payloads for GitHub, Stripe, Slack, Discord, and other popular webhook formats

Common Questions

Why do I get a CORS or "Failed to fetch" error? Browsers block cross-origin requests unless the server opts in. The request may still have reached the server — copy the cURL command and run it from a terminal to confirm without CORS limits.
How do I test a webhook endpoint before deploying? Send test payloads to your endpoint URL and inspect the response to verify it handles requests correctly.
How do I generate a cURL command for my API call? Build your request in the UI; the cURL command updates live and can be copied with one click.