Can you recover a failed webhook? Try the 503 → 200 challenge

[DimaGutierrez]

One event. Two outcomes. What would you inspect first?

Webhook Lab is a small, local Python + FastAPI workbench for capturing, inspecting and replaying webhooks. This first release is ready for hands-on feedback.

The 60-second challenge — after installation

1. Follow the quick start.
2. Click Send sample event.
3. Replay it to Demo · unavailable (503).
4. Replay the same event to Demo · accepts (200).
5. Open Replay history: the failed attempt should still be there alongside the successful one.

The Demo destinations are simulated inside the app. For a real local HTTP connection, follow Replay to your own service.

What I would like to learn from you

Comment with the first detail you needed but could not find. Was it a payload field, a response detail, a timestamp, or something else?

Use this short format if it helps:

My stack / OS:
Did the challenge work?
The confusing part:
One change that would make this useful at work:

A small reproducible bug is more useful than a generic thumbs-up. If you found one, open an issue with a synthetic event and the steps.

Current scope: single-user local prototype, SQLite persistence and manual replay. Automatic retries and public hosting are not shipped. Use fictional payloads; do not post tokens, private inbox URLs or customer data.

English and Spanish replies are welcome. ¿Lo probaste? Contame qué funcionó y qué te faltó para entender el fallo.