# Re-Sub - Wrong timestamps **URL:** \ **Category:** API\ **Created:** [May 20, 2017, 10:48am UTC](https://staging-discuss.dev.twitch.com/t/re-sub-wrong-timestamps/10420 "2017-05-20T10:48:27Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![VitruxPT](https://d1d6mrmdu7ztse.cloudfront.net/user_avatar/staging-discuss.dev.twitch.com/vitruxpt/32/2242_2.png) [@VitruxPT](https://staging-discuss.dev.twitch.com/u/VitruxPT)\ **Post date:** [May 20, 2017, 10:48am UTC](https://staging-discuss.dev.twitch.com/t/re-sub-wrong-timestamps/10420/1 "2017-05-20T10:48:27Z")
Hey guys, We still don’t have a parameter ‘ **`changed_at`** ’ or ‘ **`updated_at`** ’ for re-subscriptions. If a sub cancels his plan and re-subs again in a **30 day period** the sub streak continues the same for alerts in chat (now via **USERNOTICE** ) but the ‘ **`created_at`** ’ field in the API changes to the re-sub time which makes sense but now we have 2 different values for the time. In chat we can see that the user has been a sub for example, 12 months, **but according to the API the user has only been a sub for example, 5 months**. In chat: ![](https://d2spem0quai2ol.cloudfront.net/original/2X/c/c2430c0363f8300f831736909e48662da4373aeb.png) In the API ![](https://d2spem0quai2ol.cloudfront.net/original/2X/5/513d4380d0cf1057e347f21875e01366afce0d18.png) In my head the ‘ **`created_at`** ’ field should stay the same even if the user cancels the subscription but it’s still in the 30 day period and there should be an ‘ **`updated_at`** ’ field that would only be available if the user re-subbed **in that 30 day period after canceling the subscription**. (The ‘ **`updated_at`** ’ field would state the time of the re-subscription) Are there any plans on adding that new parameter so developers can keep track of the time a user has been subscribed without having to store this info periodically? This way we could keep using the ‘ **`created_at`** ’ field. @xangold @DallasNChains 😉 ps: This happens in both endpoints: [https://api.twitch.tv/kraken/channels/:channel\_id/subscriptions/:viewer\_id](https://api.twitch.tv/kraken/channels/:channel_id/subscriptions/:viewer_id) and [https://api.twitch.tv/kraken/channels/:channel\_id/subscriptions](https://api.twitch.tv/kraken/channels/:channel_id/subscriptions) ---
**Author:** ![3ventic](https://d1d6mrmdu7ztse.cloudfront.net/user_avatar/staging-discuss.dev.twitch.com/3ventic/32/298_2.png) [@3ventic](https://staging-discuss.dev.twitch.com/u/3ventic)\ **Post date:** [May 20, 2017, 4:25pm UTC](https://staging-discuss.dev.twitch.com/t/re-sub-wrong-timestamps/10420/2 "2017-05-20T16:25:07Z")
The subscription _streak_ is X months, but this _specific_ subscription was started on `created_at`. I would like to see the consecutive months amount in the API though. ---
**Author:** ![DBKynd](https://d1d6mrmdu7ztse.cloudfront.net/user_avatar/staging-discuss.dev.twitch.com/dbkynd/32/2144_2.png) [@DBKynd](https://staging-discuss.dev.twitch.com/u/DBKynd)\ **Post date:** [May 20, 2017, 11:40pm UTC](https://staging-discuss.dev.twitch.com/t/re-sub-wrong-timestamps/10420/3 "2017-05-20T23:40:16Z")
I’ve also noticed that the ‘streak amount’ and the `created_at` parameter are mismatched after a short lapse or even just a payment method change. I agree that some sort of `streak_created_at` or at the bare minimum a `streak_length` parameter(s) would be of use to many people without having to maintain our own database for such things. Unless I’m missing an endpoint that shares a users streak length somewhere else? ---
**Author:** ![system](https://d2spem0quai2ol.cloudfront.net/original/2X/0/05909729875cce3b53e59d5561c4d23bb14948fc.png) [@system](https://staging-discuss.dev.twitch.com/u/system)\ **Post date:** [June 19, 2017, 11:40pm UTC](https://staging-discuss.dev.twitch.com/t/re-sub-wrong-timestamps/10420/4 "2017-06-19T23:40:20Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.