Still no way to specify --stripe-version with listen?

[zircuitz]

Referencing issue #213, since it's closed, but not resolved.

Why is this still an issue?

I am running a local test environment that uses a package that relies on an older version of the API. Currently: There is no way for me to test the integration locally with the matching API version it uses, since I can't specify the API version the CLI uses with listen command. Why is that? Why can't I specify it? And why can't I just set the default version to what I actually need through the dashboard directly?

It's just frustrating having these limitations, since I have no control over the package I'm using to integrate Stripe with my website. I'm essentially forced to not use it, and do all the extra work to handle it myself. Or I could wait for the original maintainer to update it. I could also upload the project to an internet accessible server to test the webhooks directly, but at that point: What's the point of having the CLI at all?

Any consideration to fix this would be greatly appreciated.

Thank you.
Alex

[DevinWalker]

Our development team is also experiencing issues with this, which is causing problems with webhook events.

Original message from my developer:

We have a development-related question for our StellarPay

For our API calls to create and update subscriptions, we use the API version 2024-06-20, which works fine in most cases. However, when listening to API calls via the CLI, we have noticed that some webhook events like invoice.paid return a different API version (2025-04-30.basil). Because of this, the webhook payload format is different than expected and breaks our code, which makes development and testing very difficult.

We looked at the CLI docs and found the --stripe-version flag, but it seems that it does not work with the listen command.

Is there any way to bypass this problem or force the CLI to use the same API version (2024-06-20) when returning webhook events?

[ravinderk]

This is a crucial issue that continues to impact local development and testing for many of us. I'm glad to see it being revisited, as the current limitations with the stripe listen command are incredibly frustrating.

[Rahmon]

I fully agree. This limitation makes local testing difficult. Stripe’s developer experience is usually great, but not being able to specify the Stripe version adds unnecessary friction in the development workflow.

[pramodjodhani]

Big +1 on this. The ability to specify the API version for webhook events with stripe listen is a must-have feature.

[1dlef]

Hoping stripe team sees this issue, it affects testability of our application.