#_webhooks
tame martenBOT
đ 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/1405920195129770080
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
edgy nova
Hi, we have some backwards compatability support: https://docs.stripe.com/sdks/stripejs-versioning#breaking-changes
If we do decide to deprecte something, we typically let you know and surface it here: https://docs.stripe.com/changelog to ducument what API version we do that in
mighty prism
Gotcha, but, if you need to pick one to use, which one would be more appropriate?
Or both are equaly good to go without any future concerns
edgy nova
I would use Price
You can now model subscriptions more flexibly using the Prices API. It replaces the Plans API and is backwards compatible to simplify your migration: https://docs.stripe.com/api/plans
mighty prism
Ok, so going through items -> data would be more appropriate
edgy nova
yes, that is the more modern approach and the recommendation: https://docs.stripe.com/api/prices
mighty prism
ok, thanks