Webhook Catcher
A lightweight, disposable webhook reception and debugging tool that provides a temporary HTTPS URL for capturing and replaying POST request events. Events are retained for 24 hours and stored using a ring-buffer mechanism.
Timeline (last 90 days)
The webhook catcher built by the developer specified "store at most 100 events" and was implemented with a ring buffer, causing the 101st through 112th events to be silently lost when the Stripe test suite sent 112 webhooks in a burst.
The developer fixed the silent-loss problem through three strategies: modeling overflow as a first-class event (generating a {type: "overflow", dropped: N} record), having the read API return a truncated boolean field, and exposing the max_events capacity limit in the creation response.
The response that creates the catcher includes a max_events: 100 field, so the caller knows the contract boundary before sending the first POST.
The webhook catcher has been packaged and released for use by webhook receivers that need to respect their own limits.
All Facts (4)
The response that creates the catcher includes a max_events: 100 field, so the caller knows the contract boundary before sending the first POST.
50%UnverifiedThe webhook catcher built by the developer specified "store at most 100 events" and was implemented with a ring buffer, causing the 101st through 112th events to be silently lost when the Stripe test suite sent 112 webhooks in a burst.
50%UnverifiedThe developer fixed the silent-loss problem through three strategies: modeling overflow as a first-class event (generating a {type: "overflow", dropped: N} record), having the read API return a truncated boolean field, and exposing the max_events capacity limit in the creation response.
50%UnverifiedThe webhook catcher has been packaged and released for use by webhook receivers that need to respect their own limits.
50%