#daave_api
lusty shardBOT
đ 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/1292862628015771728
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
stoic valley
Hello
steep jetty
Hey!
stoic valley
Pretty sure this is not possible and you would need to use separate Meters here
steep jetty
I see, i thought that might be the case but was cautious I missed something.
Seems it was available in the legacy system since you could POST directly to the subscription items?
stoic valley
Yes that's correct -- the newer Meters API was designed a bit differently.
I can submit feedback internally about this
But yeah right now you would need separate Meters for something like this
steep jetty
is there a deprecation timeline on the legacy system?
is it still recommended to use that in this case?
stoic valley
There is no deprecation timeline at the moment. However the recommendation is to use the new API.
There won't be any further development of the legacy usage record system
And I can't guarantee it won't be deprecated at some point in the future (though that would come with plenty of communication and a timeline for migration as many users do use that API right now)