#razor2359
1 messages · Page 1 of 1 (latest)
Hello
No there isn't a way to stop these endpoints from being disabled.
You need to reliably respond to the Webhook otherwise the endpoint will be disabled
is there a better solution that we could deploy? we are using tailscale funnels and ngrok to forward the webhooks to test suites and to developer machines during development and CI.
if a developer is developing for their 1 machine, stripe will send the wehbook to all "test mode" machines, but only the developer doing the test will return a successful response
as you can see, we are constantly re-enabling webhooks
Hmmm not really... you could delete the previous endpoint each time you test using (https://stripe.com/docs/api/webhook_endpoints/delete) and then create a new one using https://stripe.com/docs/api/webhook_endpoints/create so that it is active
That is the only way I can think of to programmatically handle this