-
Notifications
You must be signed in to change notification settings - Fork 123
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Manage Webhook Endpoints #141
Comments
@tansengming - I was looking at this issue. I was wondering if there is support to manage which API version of the webhook you want to use when upgrading webhook versions. As stated by step number 2 here under webhooks. https://stripe.com/docs/upgrades#how-can-i-upgrade-my-api |
@clwang here's a way to force the API version with the ruby client https://github.com/stripe/stripe-ruby#configuring-an-api-version |
@tansengming - This only controls the API version of the requests going to Stripe, but the webhooks API version is based off the version you set when setting up the webhook API endpoint. If you need to upgrade the API version for the webhook endpoint address, you need to recreate one. I was just seeing if there is a feature in the stripe-rails gem that would allow you to specify or reject webhook requests based off the a version you configure for testing or upgrade purposes. |
Hi @clwang apologies for giving you the wrong answer, then forgetting to get back to you with the right one. The short answer is: No. Nothing in the gem let's you reject webhook requests based off a configured version. https://github.com/tansengming/stripe-rails/search?q=api_version&unscoped_q=api_version The Stripe Webhook Docs do mention an optional api_version argument. So if someone decides to build this Webhook Endpoint management feature, it'll be a good place to start. |
@tansengming @clwang I am receiving #178 when application receive web hook from Stripe. Can you please comment |
The Stripe API allows management of webhoook endpoints through the API. I wonder if this might be a useful addition to the gem.
The text was updated successfully, but these errors were encountered: