#waldeedle_webhooks

1 messages ¡ Page 1 of 1 (latest)

maiden latchBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1219419143917273099

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

fleet barnBOT
mossy vine
#

Hi, can you share the specific event ids that are failing? The event ids would start with evt_123zcx

quartz lark
#

evt_1OvjYQKjI0M1O6BOKYsqhsCG is one example

#

you can ignore the acceptance failures those were valid cases since i did not deploy there with the new sdk

mossy vine
#

Thank you, taking a look

quartz lark
#

I believe I got the error due to stripes api version warning but just double checking here

#

Received event with API version 2022-11-15, but stripe-go 76.21.0 expects API version 2023-10-16. We recommend that you create a WebhookEndpoint with this API version. Otherwise, you can disable this error by using ConstructEventWithOptions(..., ConstructEventOptions{..., ignoreAPIVersionMismatch: true}) but be wary that objects may be incorrectly deserialized.

mossy vine
#

It looks like you're moving from one major API version to another and it's possible that the payload changes as there are breaking changes. From looking at this event, evt_1OvjYQKjI0M1O6BOKYsqhsCG you shared you responded with {"errors":[{"code":"INPUT_ERROR","message":"Invalid input."}]} which you'd need to debug on your end on what input exactly you're looking for.

We document how to upgrade the API version here, https://docs.stripe.com/upgrades#upgrade-and-test-your-webhooks in relation to webhooks.

quartz lark
#

I guess the error is all I need to silence cause there are no documented breaking changes on stripe's side

#

does stripe have a defined way/best practice around the migration of the webhook? How to coordinate the events when I am deployed my new go code to production essentially

#

I don't want to drop events and since my new code in theory (I will test) should work without any changes would I just deploy and then move the api version in the account up

mossy vine
#

We recommend that you update your webhook to handle both versions, one for each. Then, test the events on the new webhook version to ensure that it works as expected.

quartz lark
#

and theres no coordination required outside of that to keep in mind? (from stripes end/what i control in the dashboard)

mossy vine
#

That is correct, as long as you're handling both versions of the webhook.

quartz lark
#

sweet thanks that assures me im heading in the right direction!