Watching a stream of UnifyPort webhooks with Pipedream RequestBin

What it does

RequestBin hands you a durable URL that records every request in a scrollable history — headers, raw body, query string, timing — and keeps them around so you can come back hours later. A replay button re-sends any captured request, which is what makes it more than a passive viewer.

When to reach for it

• Watching a sequence. One message can fan out into message.received followed by several message.status.updated events. RequestBin lays them out in order, so you can confirm the whole sequence actually landed.
• Auth flows that unfold over minutes. QR and pairing flows emit account.auth.required, account.auth.succeeded, then account.started seconds to minutes apart. A durable bin catches them all without you babysitting a terminal.
• Replaying while you iterate. Capture a delivery once, then replay it against your handler as you change code — faster than coaxing the provider into firing the same event again.

Inspecting a UnifyPort delivery

Every delivery carries the standard signing headers:

…and the normalized event envelope — the same shape across providers, so you build your handler against it once:

When not to reach for it

• Production or PII traffic. A RequestBin URL is public and guessable — anyone with the link can read every captured request. Keep it to throwaway test events.
• Forwarding to localhost. RequestBin captures; it does not forward to your machine. For that, reach for smee.io or ngrok.

Alternatives we like

• webhook.site — faster for a one-off "is anything arriving?" check.
• smee.io — forwards to localhost instead of just capturing.
• ngrok — full local tunnel with a built-in inspector at 127.0.0.1:4040.

Common questions

How long does Pipedream RequestBin keep requests?

Long enough to watch traffic accumulate across a session — far longer than a quick check needs. Exact retention depends on your Pipedream plan, so treat captured requests as test data, not an archive.

Can I replay a captured request to my local handler?

RequestBin replays to the original target. To get deliveries onto localhost, forward them with smee.io or tunnel with ngrok, then replay there.

How is this different from webhook.site?

Both capture and display requests. webhook.site is fastest for a single "did it arrive?" check; RequestBin is better when you want a durable, scrollable history of many deliveries over time.