#ivaylo-vasilev_webhooks

1 messages · Page 1 of 1 (latest)

sharp lindenBOT
#

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

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

lethal valve
#

👋 happy to help

#

this depends on the API version you're using

#

each PHP SDK version is pinned to a specific API version

mighty patrol
#

Ok but how we know which of depreacated fields from the main object will still exist in the webhooks payload that we receive. I am using 17.4 SDK which 2025-06-30.basil API. And when I see the docs for the Invoice object I can't see the payment_intent field.
https://docs.stripe.com/api/invoices/object?lang=php&api-version=2025-06-30.basil

#

But if you see the payload from the event I sent you above you will see that we have payment intent field

lethal valve
#

in the api you can choose the version of the SDK and it will show you the structure of the object in that version

mighty patrol
#

I think you are not understanding may question

#

I saw already the versions change log and so on

#

I am asking you why if a field is deprecated in the SDK still exists in the webhooks after that

#

and where I can find the structure of the webhooks, and not for the objects

#

I sent you an webhook event ID. Please check it and after that see the link I sent you

lethal valve
#

I am asking you why if a field is deprecated in the SDK still exists in the webhooks after that
it depends on the API version that the webhook is using

#

I'm kind of missing something

#

you're using the CLI

#

right?

#

the API version of the event is 2025-07-30.basil

#

that API version corresponds to v17.5.0

mighty patrol
#

Yes stripe-cli 1.29

lethal valve
#

and the event sent through the CLI to your code doesn't have a payment_intent object

#

is that what you're looking at? or are you looking at the event in your workbench on the dashboard?

mighty patrol
#

I am looking in the event in the dashboard

#

I am testing directly with our test account

lethal valve
#

ok now it makes sense

#

the event shown on the dashboard follows the structure of your account's default API version which is 2020-08-27

#

if you want you can upgrade your default API version to the latest

mighty patrol
#

Ok, then

#

Is there any chance to upgrade it to one version behind directly from the dashboard?

#

And is there any way to send the hooks with the newest version only for specific stripe-cli instances (when we are talking about the testing account, that is used from several developers )?

lethal valve
#

Is there any chance to upgrade it to one version behind directly from the dashboard?
I think we only offer upgrade to the latest

mighty patrol
lethal valve
#

you can create sandboxes

mighty patrol
#

ок

#

thanks

#

for the help man

#

Have a nice one

lethal valve
#

would you mind me closing the thread if you don't have any other questions?

sharp lindenBOT