#lachiu_best-practices

1 messages ¡ Page 1 of 1 (latest)

hallow hollowBOT
#

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

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

clever ginkgo
#

Hey there, ultimately this depends on the API version you use when making requests. Using versions prior to March's basil release still supports legacy metered pricing.

#

This would apply, for example, if using versions of SDKs prior to that release (due to version pinning) and/or accounts predating that change with an older default API version.

#

Can you share an example of how this is failing for you with your prior integration?

#

Creating a sandbox on an existing account with an older API version should be assigned that same default API version on the sandbox

faint dust
#

I apologize for not being clear enough. This isn't about our API version. This is about the web ui not allowing us to create new legacy metered products, in either sandbox, test or production environment.

clever ginkgo
#

Do you mean in the Dashboard specifically?

faint dust
#

Yes

#

So my initial message was about it being ok if it's in production, breaking changes and all.

Not being able to replicate our test environment from the dashboard in the sandbox environments you provide is going to delay any implementation of the sandbox as we can't allocate that much time in our current dev cycle. So we were hoping to get a backdoor option to still create these.

clever ginkgo
#

Gotcha, I can't say for sure as I'm not familiar with all Dashboard behaviour, but I don't think the Dashboard still supports that. You should be able to continue creating these via the API, though, assuming your code had been doing that before.

faint dust
#

We've only been adding usage records via API

clever ginkgo
#

Hmm thinking about this

#

So you've been using usage based billing with Usage Records, but you've only ever created the products/pricces via the Dashboard, correct?

#

And now with these changes and Meters for usage-based billing, you can't create new test/sandbox prices using the Dashboard like you've done previously?

#

I can flag this feedback internally. Assuming I've understood you correctly, I agree this is not a great experience for you.

#

You could even just take the curl examples and edit them manually to execute for one-off creation

#

The "Stripe CLI" snippets are also compatible with the workbench shell in your Dashboard