#danf-sh_api
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/1359938803363741776
๐ 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.
- danf-sh_unexpected, 5 days ago, 39 messages
Hello ๐
Yes this is one of the breaking change we flagged for the lastest API version.
Stripe Java SDKs are pinned to specific API versions to ensure the objects returned from the API match the expected definition in the SDK
Is there any plan to fully deprecate these older apis, will they be sunset?
The existing APIs will continue to work. We won't fully deprecate without A LOT of communication about the upcoming changes so that you can adjust your integration. However, the docs for these APIs will be harder to find
You might want to bookmark this doc as we no longer provide an easy way to find it.
Am I able to use both reporting methods for a single price? For example, if I want to migrate to the new apis, can I add a meter to an existing price that doesn't have one. Still be able to report usage the old way, then change the code to use the meter based apis?
I'll be honest, I haven't tried that. I think it should work as meter events and usage records are separate. I would recommend building a test mode simulation to validate the expected behavior
Okay I can give that a try. Are there any other links you might have about this change? I looked through the release notes for the client code but it wasn't that specific to the usage updates. Or do the links you shared pretty much cover it?
I would recommend using Test Clocks to make sure you cover multiple billing cycles so you can test out the scenario where you have an ongoing subscription and switch over from usage records to meters.
Unfortunately, I think the changelog is the most detail we provide
Alright, sounds good, thanks for the help!