5 ms·

Good tips! I actually just worked on detecting dead webhook endpoints, as I've had a number of users use ngrok for local testing, create hundreds of events, and

by ezekg 9y ago

Good tips! I actually just worked on detecting dead webhook endpoints, as I've had a number of users use ngrok for local testing, create hundreds of events, and then disable ngrok--and much like Stripe, I retry with an exponential backoff over the course of a few days. Needless to say, my logs were filled with failed webhook request errors and I had to figure out how to limit that from happening in the future. Very interesting list of alternatives to webhooks as well.

jkarneges 9y ago
When it comes to axing dead endpoints, I see two ways to handle this based on the way webhooks are configured. * If webhooks are configured by UI, then you have to contact the user and tell them their webhook is gone, e.g. via email. * If webhooks are configured programmatically, then the endpoints ought to be able to be swept up silently, and the receiver should know to periodically refresh the configuration for as long as it cares about it. Ideally all webhook implementations would work the second way, but unfortunately it is not standard practice.