Subs Tenure in Helix
We would like subs tenure in Helix in order to use this for merch extensions providing tenure-based merch options.
-
XcomReborn
commented
I would like this information so I can display a wall of fame I created for the subscribers and the number of months they have subscribed/ subscription streak. It seems crazy that I have to wait for them to talk in change to cache that information from the badges. Why isn't this available at the subscriber endpoint. The fact that this information is available in chat means it isn't private information so what is the reason for this ?
-
EvilJordan
commented
Just ran into this. HOW is this data still not available data in 2026??
The existing API (/getSubData) does not contain enough information to be useful. Additionally (and offered as an alternative by Twitch), the exported CSV (Analytics > Overview > Export Data) does not meet the need, either, as it doesn’t include: exact (gifted) sub time, gifted by whom, and to whom it was gifted. At a minimum, it should be “X user gifted Y subs, at this level, at Z time.” The export also doesn’t include a list of who subscribed for themselves and what day they did it.
It’s easy to get a list of top subscribers, but not the day they started.
This is pretty big issue for non-traditional streamers (you know what I mean) coming over to Twitch and being unable to run the same kind of analytics they’re used to. It's also a problem for every other streamer looking to reconcile the activity they see in their stream with the payouts they receive from Twitch.
-
Stoopler
commented
Six years later, why isn't this a thing? Why should I have to scrape chat to get the number of months subscribed when this should just be added to the events.
-
MasterBowtie
commented
I would like to add my vote to this topic. This could also help keep track of the most recent subscriptions and/or resub to said channel
-
socramdavid
commented
Having this info in https://dev.twitch.tv/docs/api/reference/#check-user-subscription would be very useful.
In my case, I would use it to give subscribers different benefits outside of twitch (i.e, access to a game multiplayer server) based on their subscription duration. -
Dekron_
commented
it should be added to GET https://api.twitch.tv/helix/subscriptions
having more information, for example the create and update time of a sub and the number of months, give a lot more iteraction and integration possibilities.
-
TheVortexHero
commented
Allowing broadcasters (or moderators of a broadcaster) to see the subscription lengths of their subscribers or allowing viewers to see the subscription length of channels they are subscribed to only for their own subscriptions would be a great addition to the APIs.
If this change is implemented, I plan on using this API to integrate a Discord bot that shows sub-badges for a broadcaster’s viewers next to their display names on Discord. This Discord bot would work by having the broadcaster or a moderator log in to Twitch to generate a user token to access the appropriate APIs. Then, by using the Twitch connections already linked to a Discord user’s account with Discord’s native Twitch integration, I would assign roles to users to display their sub-badges next to their display name.
-
mediometrus
commented
Hi Twitch, this is a really important and necessary information. Let say you want to do ruffles in your channel in which only most loyalty subscribers could have access to (or subscribers over a certain loyalty).
Theres no way to do it with the actual data we have access now as EventSUB channel:subscription:message is not always sent, for example on automatic Resubs.
Please include this information or always generate a channel:susbscription:message on Subs or Resubs (being msj "" or void if the users does not specifies one but include the actual info it offers).
-
MJRAMON
commented
https://api.twitch.tv/helix/subscriptions/user should really also return amount of months user is subbed and sub streak length
-
JeffSkye
commented
As a broadcaster you already have access to this data in the CSV file.
It would really help out if, with a Oauth scope, a developer could access this data as well. Automating the process and making full use of the data that is already there.Right now broadcasters would have to download the .csv file daily and then upload it to whatever system they created.
Which is both a safety concern, data leak, and big hassle.
-
CSF_RS
commented
This would be really useful for both our DMs tool, but also the analytics.
-
RetroGamerRyan
commented
I'm going to lose an important community feature when the v5 API shuts down because of this. Please add at least the updated_at field to the channel:read:subscriptions scope results!
-
JeffSkye
commented
I would really like to see this feature. This would be a big help in rewarding subs for their sub streaks outside of Twitch. With for example Discord bots etc.
-
MembTV
commented
we need sub duration information, is super important, streak etc etc....
-
ExpertsOnline
commented
Really sad to see that v5 is being decommissioned with no migration path to helix for this information. Although v5 information was inconsistent at time, it was still much better than no information at all.
-
Swiftor
commented
I'd also REALLY like to see this - having this information allows us to easily reward people for keeping their sub streak, for example:
- giving longer streaks better odds of getting into games
- more points (I use my own system) for longer term subs
- maybe an automatic invitation to get a small physical gift on streak anniversary'sit's easier than ever for someone to let their sub streak expire (gifted subs, twitch prime, etc.) - giving a stronger reason to care about keeping it going is more important than ever.
-
mell0w_7
commented
I need this aswell for a game i am making. The longer the user is subscribed the stronger he gets in my game. So i need this pls!!
-
martinotu
commented
This could be very useful!
I'm working on automating Telegram group handling based on Twitch subs and I would benefit a lot from knowing how many months a specific user is subscribed for! -
JustJVA
commented
My particular use case is a monthly lottery system based on whose subbed for a particular month and who gifted subs for a month. if the created_at and updated_at from the legacy version could be included in the new version that would be awesome
-
wolf_the_ai
commented
First date subscribed would be helpful as well. Despite not being able to maintain their subscription for the entire time I have broadcaster request to find out when viewers first subscribed.