@sundheden the endpoint you’re giving has the same information as the one I’m hitting.
@george
That’s materially incorrect. v5 was introduced sometime mid 2015 as judged from google trends, sub streaks have existed since Jan 2015. Kraken hasn’t (to my knowledge) existed in production since Jan of 2015. Regardless, just because your tire’s been flat for 3 years doesn’t mean you don’t change it before going for a drive.
@Dist, if the purpose of the API is to provide useful data to developers and that data is materially incorrect and not fit for purpose (as in created_at not matching sub streak start date) that’s pretty much the definition of an API bug. I can say with confidence that the majority of the consumers of this particular api have absolutely zero interest in when the subscription started from a billing standpoint, but do have interest in when it started from within the context of a sub streak, considering sub streaks have been a thing for nearly 4 years now.
Please note that I said that if twitch wanted to add the object that they’re referencing to actually calculate badges/streaks to this particular endpoint, I’d be fine totally with that solution as well. created_at, however, is currently only valid from a backend billing context, which makes it wildly inaccurate at best for most API consumer purposes and a potentially embarrassing data leak at worst (in the case of someone having billing/financial issues).
Regardless, twitch has the data and they’re not publishing in the place where logic dictates it should be.