#brettskibrettski-api-ref

1 messages · Page 1 of 1 (latest)

torn salmon
#

Hello! Starting up a thread for you

#

There is no way to force the docs to show a specific API version, but what specifically are you trying to do? If there's a specific parameter or request you have a question about I can definitely help with that

royal wedge
#

Well I have noticed that things have changed, e.g. around checkouts, and since we are unable to move to the new api at this time, I want to ensure I am configuring things correctly for the api I am programming against

torn salmon
#

Gotcha - a better resource to look at may be the API changelog (https://stripe.com/docs/upgrades#2022-08-01) - it talks about all the backwards incompatible changes that were made in each API version, so you can check what Checkout changes were made in the most recent version

Keep track of changes and upgrades to the Stripe API.

royal wedge
#

That's not great, now I am looking at two references to make changes. Ugh

#

I guess there is no way, thanks for your time.

torn salmon
#

Alternatively, the API reference also has callouts about which parameters have changed compared to your api version

#

here's an example

royal wedge
#

I noticed, but they are not all up to date yet so I was worried about missing something

#

So now I have no reference to this field which is heavily utilized in our codebase

torn salmon
#

Yeah that's a downside of the API reference - it doesn't call out which fields are removed, it's mostly caling out which behavior has changed on fields that are still present

#

I also see you typing in the main channel - if you have other questions you can just ask them here

royal wedge
#

Oh, okay. I didn't know if you 1 question per thread was preferred

torn salmon
#

Backing up for a second, is your goal to allow customers to provide a promotional code (the name, not the ID) during the Checkout Session, or do you want to apply the promotion code during creation?

royal wedge
#

apply promotion during checkout creation

#

This way the customer doesn't need to type in a code, we handle it on the web app side

torn salmon
#

Gotcha

royal wedge
#

wow, really? :sigh:

torn salmon
#

Yeah, sorry this isn't easier - the promotion code is meant to be customer-facing and not used during creation (they'd input it while completing the session)