Report abuse, unwanted requests or a security problem
If a webhook.stream URL is being used against you, or your server is receiving deliveries you didn't ask for, here's how to identify the source and get it stopped.
webhook.stream automations send requests on their users' behalf, and test URLs are public addresses. If either is being misused, tell us and the URL will be disabled and its data erased.
If your server is receiving requests from webhook.stream
Every request an automation sends identifies where it came from:
| Header | Tells you |
|---|---|
User-Agent |
Starts with webhook.stream/1.0 |
X-Webhook-Stream-Endpoint |
The ID of the webhook URL whose automation sent it |
X-Webhook-Stream-Request |
The ID of the request that triggered it |
- Find one of the unwanted requests in your server's logs.
- Copy the value of
X-Webhook-Stream-Endpoint. - Email it to [email protected], with roughly when the requests arrived and anything else you know.
Until it's dealt with, you can block requests with that User-Agent or endpoint header at your server or firewall.
If a webhook.stream URL is being used against you
For example, a webhook.stream address in a phishing message, or one collecting data it shouldn't. Email [email protected] with the full address (https://in.webhook.stream/…) and where you found it.
Webhook URLs can't serve web pages, set cookies or redirect visitors, so a link to one can't impersonate a site. But we still want to know.
To report a security vulnerability
Email [email protected] with the details and the steps to reproduce it. Please give us a reasonable chance to fix it before you disclose it, and don't access data that isn't yours while testing.
If it's your own URL
If you made the URL and it's sending somewhere it shouldn't, open its inspector, click Automations, and switch off Enabled or Remove the automation, then Save. Or delete the URL with ⋯ → Delete this URL.
