#manny-manny-2023_webhooks
1 messages · Page 1 of 1 (latest)
👋 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/1395037126378258554
📝 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.
- manny-manny-2023_webhooks, 3 hours ago, 35 messages
hi
our stripe default api version is 2022-11-15 we are upgrading stripe java version to 28.4.0 and we created stripe webhook for 2025-02-24.acacia but stripe cli forward events is still using 2022-11-15, how to make it work for 2025-02-24.acacia please tell
Gotcha, looking in to this.
Can you send the CLI commands that you are using here? Are you testing this by resending events or creating new ones?
stripe listen --forward-to localhost:8080/webhook/paymentCheck
Ready! You are using Stripe API Version [2022-11-15]. its saying apart from whsec key
cli version 1.28.0
Ah, that is your account's default version. According to our CLI ref, the listen command can only either use your account's default API version or the latest API version if you use the --latest flag
https://docs.stripe.com/cli/listen#listen-latest
yes but the data object is not getting deserialized if i use latest it should be 2025-02-24.acacia for proper deserialization i think
You aren't using the --latest flag in your CLI command, so we default to your account's default version, which is the 2022 one.
i tried with latest just now
Can you send me the ID of an event that got sent to that endpoint when using --latest?
this is the output i am getting in java
event version: 2025-06-30.basil
stripe version: 2025-02-24.acacia
Yep, was just about to mention that, basil is the latest API version
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
i am able to get the event in backend but the thing is this line is failing EventDataObjectDeserializer deserializer = event.getDataObjectDeserializer(); --> even though payload has data object its not converting
So that flag is functioning correctly there. So the two main ways for you to test with an acacia endpoint will be to:
- Create an endpoint via the API like you did before but while specifying acacia, test with that endpoint (ngrok and similar utilities can be helpful for that)
- Write in to our support team and ask them to set your account's default version to acacia (unfortunately you can't do this yourself)
Is there a specific error the deserialization is failing with?
So no error is thrown but that is happening? And what java SDK version are you using?
java 21 and stripe java 28.4.0
Gotcha
And to be clear, the deserialization is failing when you use the 28.4.0 library with your stripe listen ... --latest webhook endpoint that uses basil?
yes
I think that is expected, 29.0.0 is when that stripe-java starts using basil
yes 29.0.0 have lot of changes which disrupts some of functionalities so we opted for 28.4.0
Gotcha, so the two ways to test with acacia that I mentioned above are what you will need to do
also this link says we have a flag but that flag is not working https://docs.stripe.com/stripe-cli/overview
That –stripe-version 2025-06-30.basil flag is specifically for CLI commands that make a single API request. For stripe-listen specifically the CLI ref says:
The listen command can receive events based on your account's default API version or the latest version
https://docs.stripe.com/cli/listen
ok so for using ngrok can we give the ngrok url with the same events for another webhook, will 2 webhooks work paralelly without issue?
Correct, you can have webhook endpoints with many different API versions at once. There is a limit but it should be plenty for your testing here
ok thank you so much for your help, we will try these and get back to you for any blockers , thank you so much