#50an6xy06r6n_api

1 messages · Page 1 of 1 (latest)

wide gulchBOT
#

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

📝 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.

radiant slate
#

If you have an older sdk, you'll have to upgrade to a newer version to take advantage of new features, api params, etc. Same with allow_redisplay.

#

Also, was a change made to the documentation website to no longer show older SDK versions? It seems like they only go back about a year, which is extremely inconvenient.
What page are you referring to

#

Can you link

polar vine
#

I'm referring to the dropdown on https://docs.stripe.com/api that lets you select your sdk version. It used to go way further back and I think synced with the SDK version on your Stripe account.

Stripe API Reference

Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.

#

the allow_redisplay change is really annoying because it used to redisplay by default, but then the behavior was changed, causing a regression in our flows

radiant slate
# polar vine the `allow_redisplay` change is really annoying because it used to redisplay by ...

Yeah there were comms about this a while back. This has been in place almost a year now: https://support.stripe.com/questions/prefilling-saved-cards-in-checkout#:~:text=Impact to existing integrations

Prefilling saved cards in Checkout : Stripe: Help & Support

Find help and support for Stripe. Our support site provides answers on all types of situations, including account information, charges and refunds, and subscriptions information. Get your questions answered and find international support for Stripe.

radiant slate
polar vine
radiant slate
#

Yeah I think you'd have to use the wayback machine to see older

#

Unfortunately

polar vine
#

I'm curious if/why there was a decision made to limit the historical documentation, which was incredibly useful

radiant slate
#

Yeah I don't have the context unfortunately

polar vine
#

I don't think the wayback machine thing works. There's no indication of what the version you're looking at is

#

and there's basically no snapshots from before 2024

radiant slate
#

Yeah that's because we never used to show version at the top

#

You have to look at a specific endpoint's page

#

Then go to the time-frame of your api version

polar vine
#

version definitely used to be shown at the bottom somewhere. But maybe only if you were logged in

#

as I said, the snapshots only go back to a year ago, so it's not much more useful than the current system

radiant slate
#

Yeah unfortunately there's not really a better solution for older api versions

polar vine
#

has there been a conscious decision recently to stop supporting older API versions?

radiant slate
#

No they are still supported

polar vine
#

but without documentation?

radiant slate
#

Yeah we do not show the api spec for older versions currently

polar vine
#

so is it accurate to say that development on old API versions is no longer supported? Hard to do active development without docs

radiant slate
#

If you are building a new integration you shouldn't be using an older api version though

#

If it's a legacy system using an older api version it will continue to work

polar vine
#

I'm maintaining an existing integration but we occasionally want to add new features, or fix regressions. How am I supposed to do that effectively if I can't rely on the documentation to know what options are available to me

wide gulchBOT
radiant slate
#

best practice is to periodically update your api version anyway though

polar vine
#

the changelog doesn't provide a comprehensive documentation of what parameters have changed, or any number of other things that are needed to write an actual integration

ancient agate
#

Hi, taking over as my teammate needs to step away. Let me catch up.

#

Will https://docs.stripe.com/changelog/2024-06-20 work? If you click on 'Previous versions' it should show you changes from all the way from 2011. Is there a specific functionality you're looking for aside from allow_redisplay that I can address directly?

polar vine
#

no, the allow_redisplay thing is the main actionable thing for now, and it sounds like the only solution is to upgrade. My other questions were aimed at figuring out whether we'll need to be upgrading anyway to avoid losing support. Sounds like the answer on that front is a bit mixed

#

we're currently running on v2020-08-27 so it's going to be a pretty big jump regardless

#

would have been nice to have been directed to this earlier

#

It seems like the API doc changes align with the new API release process

ancient agate
#

Ah yeap! Sorry about not sharing that earlier.

polar vine
#

still doesn't seem like it was necessary to remove the docs for the older API versions... It would be nice to at least have an archived site with the older docs

ancient agate