#connor_best-practices

1 messages ¡ Page 1 of 1 (latest)

subtle groveBOT
#

👋 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/1420148338015080449

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

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

halcyon depot
#

Hi there,
I'm just repsoning to acknowledge your question. I am supporting right now another person but I will be with you shortly.

halcyon depot
#

Sorry for the delay.

Generally speaking you are already looking at the right docs. But since you are upgrading the API version 3+ years, I would recommend going through the API changelog and identify breaking changes that might have an impact on your current integration. For example 2025-03-31.basil introduced many breaking changes for billing/invoicing that you need to be aware of https://docs.stripe.com/changelog#2025-03-31.basil

I would recommend testing throughly in a test enviroment/sandbox different scenarios, using the new API version to make sure everything works as expected.

When it comes to webhook versioning, I would recommend reading through this doc: https://docs.corp.stripe.com/webhooks/versioning that helps setting up a new webhook endpoint with the updated API version.

exotic trellis
#

@halcyon depot No worries!

I've audited the changelog and have finalized my updates in support of breaking changes, so I think the API should be functioning correctly now.

Now I need to verify that the webhooks will work correctly. Is there a chance I don't need to do anything with webhooks?

#

All of my breaking changes were related to attributes I would post to the Stripe API.

Am I oversimplifying in thinking that I only need to update my webhooks version if my webhook handlers were attempting to access deprecated attributes?

(It feels naive of me, haha)

halcyon depot
#

Simplyfied? You are correct. If you do not "care" about deprecated poperties/fields, then you should be fine. Be aware since webhook API version, and your integration API version won't match, deprecated fields might be missing, but you might also not receive newer fields, that were introduced by a later API version.
So you integration and webhook endpoint might still work and that might be sufficient for your usecase (which my team obvsiously can't say), but we still recommend to update the webhook endpoint accordingly to the API version of your integration.

exotic trellis
#

Thanks a ton! This was very helpful and cleared up my confusion

halcyon depot
#

No problem. Always happy to help!