Webhook Rodeo

Showcase
, ,
1

Hey Vercel Community!

I built webhook.rodeo because every time I integrated with a new API, debugging webhooks felt way harder than it should be. I just wanted a place to see the payloads clearly, replay them when something broke, forward them reliably, and not fight with brittle dev tools or home-rolled logging servers. webhook.rodeo is the tool I wished existed:

  • Create an endpoint instantly

  • Capture and inspect incoming webhooks in real time

  • Replay and forward them to any destination

  • Verify signatures and track delivery attempts

  • Keep a clean history of everything hitting your system

It’s simple, fast, and built for people who integrate with APIs all day. If your work depends on webhooks, I think you’ll find this genuinely useful.

Oh, also very proud to say this was built entirely on Vercel using Next.js, Vercel Workflows + Queues (which should be out of the closed beta sometime in January!).

Happy to answer any questions and thanks for taking a look!

1 Like
2

Hi folks, also helped build https://webhook.rodeo

For me, it was because I got frustrated with ngrok and cloudflare tunnel trying to deal with webhooks for local development.

Create a webhooks (get a public url), then use our cli:

rodeo forward <local port, localhost:3000/endpoint>

This will forward your webhook to your local machine:

Internet → Webhook Rodeo Public Endpoint → rodeo cli forwarding → localhost:3000/endpoint

The best part is you get a full dashboard where you can inspect the payloads, retry, see headers and debug.

Been hooked on the Vercel ecosystem for the past 5 years - Vercel Queues and Workflows are probably one of the most exciting primitives to build so much more!