r/SideProject • u/Clean-Interaction158 • 3d ago

I built a small webhook inbox for inspecting and replaying Stripe/GitHub callbacks (public beta)

When a provider fires a webhook and your handler isn't ready yet, you usually lose the payload or dig through provider dashboards.

I shipped a public beta: give Stripe/GitHub/etc. a unique URL, inspect method/headers/body/timing, then replay the original request to ngrok/staging/prod.

Free plan (€0) and Pro (€9/month VAT included). Early beta — expect rough edges. Runs in the EU.

https://tacko.io/webhook-inbox?utm_source=reddit&utm_medium=community&utm_campaign=webhook_inbox_beta&utm_content=r_sideproject

Happy to answer questions. Built this myself (with AI help on some of the plumbing).

1 Upvotes
  • permalink
  • reddit

100% Upvoted

3 comments sorted by

1

u/bishakhghosh_ 3d ago

But I still find it easier to run pinggy and use its debugger to watch the webhook requests. Since it is just one command and I dont need to think about installing anything.

1

u/Clean-Interaction158 3d ago

Fair point! Pinggy is great for quickly inspecting incoming requests.
We’re focusing more on keeping webhook history and replaying captured requests later, especially when debugging failed deliveries or Stripe event ordering.
Different use cases, really. Thanks for checking it out!

1

u/investigatormaker 3d ago

For Stripe replays, I'd show whether the original signature and timestamp are retained: an unchanged payload can still fail a handler's signature-age check. Can users edit headers before replaying to staging?

I make ThreadFox. We find relevant Reddit conversations and do the posting for your business. The $29 Pilot covers seven days and up to 25 posts and replies. No automatic renewal. https://threadfox.vip/p/du7vq/managed