Frequently asked questions

webhookwire gives you a unique URL that records every HTTP request sent to it. You can watch requests arrive live in your browser and inspect their method, path, query string, headers and body. It is built for testing and debugging webhooks and API clients.

Yes. There is no paid plan. The service runs on free-tier infrastructure, so it has fixed limits: endpoints last 72 hours, keep the newest 100 requests, and accept up to 60 requests per minute.

No. Creating an endpoint gives you a private inspector key that is saved in your browser. Anyone with the key can read that endpoint's requests, so treat it like a password.

Every endpoint, together with all requests it captured, is deleted automatically 72 hours after it was created. You can delete single requests, clear the history or delete the endpoint sooner from the inspector.

Only people who have the endpoint's inspector key, which means you and anyone you share the private inspector link with. The receiving URL itself only lets people send requests, not read them.

It cannot be recovered, because the server stores only a hash of it. Create a new endpoint. The old one and its data are deleted when it expires.

GET, POST, PUT, PATCH, DELETE, HEAD and OPTIONS. Any content type is accepted: JSON is shown formatted, URL-encoded and multipart forms are parsed, text is shown as text and binary bodies get a hex view.

Bodies up to 1 MB are accepted and the first 64 KB is stored. Larger requests receive a 413 response, and their headers and size are still recorded.

Yes. You can set the status code, headers, body, content type and a delay of up to 10 seconds. This is useful for testing how a webhook sender handles errors, retries and timeouts.

You can replay any captured request from your browser to a localhost URL, or copy it as a cURL command and run it locally. Browser replay needs your local server to allow cross-origin requests from this site.

The sender runs in your browser, so the browser's CORS rules apply. If the target server does not allow requests from other sites, the browser blocks the response and hides the reason. Use cURL for those servers, or send to your own endpoint, which always allows cross-origin requests.

Avoid it. Anyone who learns your receiving URL can send data to it, and anyone with your inspector key can read it. Use test credentials and sample data, and delete captured data when you are done.

No. The inspector and request sender never show advertising, and captured webhook data is never used for ads. Ads may appear only on informational pages such as articles and documentation.

Requests over an endpoint's per-minute limit receive a 429 response and are not stored. If the service's shared daily infrastructure quota runs out, receiving URLs return a 503 response until it resets at midnight UTC.