Real-time inspection and local forwarding, forever free. Upgrade when you need history, replay, and team features.
Inspect and monitor, no commitment
For active development and monitoring
For teams shipping together
You'll see a clear error when trying to create an 11th endpoint. Your existing 10 endpoints keep working normally.
Yes. WebSocket streaming is a core feature, not a premium gimmick. You'll always see events live.
Your browser tab acts as a relay. It receives the live WebSocket event and POSTs it to localhost:PORT. No server-side tunnel required — works entirely in your browser. (Requires Chrome or Firefox)
Re-POST any stored event to any URL you choose. Useful for testing your endpoint handler without waiting for the external service to trigger again.
Yes. Cancel from the billing portal and you'll retain Pro access until the end of your billing period.
Never. Your endpoints are permanent as long as your account exists — free or Pro. Unlike some tools that delete URLs after a few days, yours stay put.
New events keep arriving and senders always get a 200 response. Once you hit 500, older events scroll out of your visible history — but they're still stored for up to 7 days. Upgrade to Pro within that window and you'll get them back.
Configure any status code, response body, and headers per endpoint. When a webhook arrives, your endpoint returns exactly what you set instead of the default 200. Perfect for testing how your sender handles failures, retries, or custom response formats — no code changes needed.
Set an absence threshold on any endpoint — 15 minutes, 1 hour, whatever makes sense for your integration. If no events arrive within that window, HeyListenUp sends a Slack notification. Add a HeyListenUp endpoint as a separate destination in your webhook source and you get early warning without adding any risk to your production path.
We'd recommend against it. HeyListenUp is an out-of-band webhook visibility tool — your production webhook URL should go directly to your app. The right pattern is to register two destinations in your sender's dashboard: your real endpoint, and a HeyListenUp endpoint alongside it. That way you get full inspection and alerting without HeyListenUp ever being in your critical path.