#bstny_api

1 messages · Page 1 of 1 (latest)

rigid ventureBOT
native hamletBOT
#

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.

rigid ventureBOT
#

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

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

wheat pasture
#

hi there!

ruby owl
#

I will try to debug further the PHP api version. but it seems right

#

Give me a moment please

wheat pasture
#

in the request you shared, no API version was set, so we used the deault API version of the account (2020-08-27)

ruby owl
#

Hmmm

I have set the Stripe::setApiVersion('2024-04-10'); in service provider, seems it does not work anyway

It must be some legacy thing deep inside the code

Thank you anyway

#

This should be the fault 🙂

wheat pasture
ruby owl
#

I don't think so, we are using some strange wrapper around, anyway it is on my head from there

#

Thank you, this helps a lot

wheat pasture
#

happy to help 🙂

ruby owl
wheat pasture
#

same as before: no API set, so we used the default one.

#

looks like you are using the Stripe CLI?

ruby owl
#

I do use the stripe CLI, can I inspect the event details?

wheat pasture
#

what command are you running exactly? to change the API version, you should use something like -v 2024-04-10

ruby owl
#

stripe listen --latest --forward-to https://foo.dev:443/webhooks/stripe --events invoice.created,invoice.payment_succeeded,invoice.payment_failed,customer.subscription.deleted,customer.subscription.trial_will_end,payment_intent.succeeded,payment_intent.processing,account.updated

Ready! You are using Stripe API Version [2024-04-10]
wheat pasture
#

can you add -v 2024-04-10 to your command?

#

oh, wait, you are using stripe listen? in this case you can only use your default API version or the latest API version

#

you cannot set a specific API version in this case.

ruby owl
#

I do set the --latest

# 
stripe listen --latest
wheat pasture
#

which API version do you want to use when forwarding the events?

ruby owl
#

'2024-04-10'

wheat pasture
#

can you add the --latest flag as mentioned in the link I shared above?

ruby owl
#

I am using it, the CLi echoes "Ready! You are using Stripe API Version [2024-04-10]"

wheat pasture
#

that's what you wanted, no? so what's the issue? I'm confused.

ruby owl
#

The request send from PHP sdk is recognized by dashboard as 2020

#

According to the logs, I am using the stripe-version header and it contains the 2024

wheat pasture
#

but these are completely different things

  • you set stripe listen to API version 2024-04-10, so the events you will receive will be from 2024-04-10
  • but that doesn't change the API version used when you make your API calls
ruby owl
#

Can I change the API version I am using without changing the default API version?

wheat pasture