# Helix Sub missing count? **URL:** \ **Category:** API\ **Created:** [February 15, 2019, 2:19pm UTC](https://staging-discuss.dev.twitch.com/t/helix-sub-missing-count/20045 "2019-02-15T14:19:00Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![SeeingBlue](https://d1d6mrmdu7ztse.cloudfront.net/user_avatar/staging-discuss.dev.twitch.com/seeingblue/32/1876_2.png) [@SeeingBlue](https://staging-discuss.dev.twitch.com/u/SeeingBlue)\ **Post date:** [February 15, 2019, 2:19pm UTC](https://staging-discuss.dev.twitch.com/t/helix-sub-missing-count/20045/1 "2019-02-15T14:19:00Z")
I noticed the new `Get Broadcaster Subscriptions` endpoint doesn’t include a count. If I am loading all subscriptions, how do I track progress if I don’t know how many I’m looking for? > **[Reference](https://dev.twitch.tv/docs/api/reference/#get-broadcaster-subscriptions)** > > Twitch Developer tools and services to integrate Twitch into your development or create interactive experience on twitch.tv. ---
**Author:** ![BarryCarlyon](https://d1d6mrmdu7ztse.cloudfront.net/user_avatar/staging-discuss.dev.twitch.com/barrycarlyon/32/253_2.png) [@BarryCarlyon](https://staging-discuss.dev.twitch.com/u/BarryCarlyon)\ **Post date:** [February 15, 2019, 2:31pm UTC](https://staging-discuss.dev.twitch.com/t/helix-sub-missing-count/20045/2 "2019-02-15T14:31:17Z")
The last page will have zero records in the data array What I do is I paginate if I have a cursor and `number of records` = `page limit` I paginate the next page. So if the last page does have 100 records the next page will have zero records. (which is less than the limit I request and I usually request 100) ---
**Author:** ![SeeingBlue](https://d1d6mrmdu7ztse.cloudfront.net/user_avatar/staging-discuss.dev.twitch.com/seeingblue/32/1876_2.png) [@SeeingBlue](https://staging-discuss.dev.twitch.com/u/SeeingBlue)\ **Post date:** [February 15, 2019, 2:36pm UTC](https://staging-discuss.dev.twitch.com/t/helix-sub-missing-count/20045/3 "2019-02-15T14:36:19Z")
@BarryCarlyon But I like to output a progress percentage as I’m reading through pages. I can’t even tell the user how long it’s going to take without knowing how many pages I will be loading and I can’t do that without a total count before I start. ---
**Author:** ![BarryCarlyon](https://d1d6mrmdu7ztse.cloudfront.net/user_avatar/staging-discuss.dev.twitch.com/barrycarlyon/32/253_2.png) [@BarryCarlyon](https://staging-discuss.dev.twitch.com/u/BarryCarlyon)\ **Post date:** [February 15, 2019, 2:37pm UTC](https://staging-discuss.dev.twitch.com/t/helix-sub-missing-count/20045/4 "2019-02-15T14:37:17Z")
Yup nothing can be done about that currently. I’ve highlighted this as a issue (no total) to Twitch Staff already. Currently highlighted issues are: - No Total - No tenure information - No Dates/start/end times ---
**Author:** ![Dist](https://d1d6mrmdu7ztse.cloudfront.net/user_avatar/staging-discuss.dev.twitch.com/dist/32/7192_2.png) [@Dist](https://staging-discuss.dev.twitch.com/u/Dist)\ **Post date:** [February 15, 2019, 4:42pm UTC](https://staging-discuss.dev.twitch.com/t/helix-sub-missing-count/20045/5 "2019-02-15T16:42:15Z")
I’ve also pointed out that the endpoint also lacks sub point info, which would be great to have. There’s an undocumented endpoint that shows how many subs are at each tier, as well as current sub points and what’s needed for the next emote slot unlock which would be very useful to have on this endpoint as well so we don’t have to call a separate endpoint, and if we only need that general information we shouldn’t need to go through every page. ---
**Author:** ![SeeingBlue](https://d1d6mrmdu7ztse.cloudfront.net/user_avatar/staging-discuss.dev.twitch.com/seeingblue/32/1876_2.png) [@SeeingBlue](https://staging-discuss.dev.twitch.com/u/SeeingBlue)\ **Post date:** [February 17, 2019, 2:59pm UTC](https://staging-discuss.dev.twitch.com/t/helix-sub-missing-count/20045/6 "2019-02-17T14:59:32Z")
Lets add that `user_name` is not consistent. This is the `Display_Name`. ---
**Author:** ![SeeingBlue](https://d1d6mrmdu7ztse.cloudfront.net/user_avatar/staging-discuss.dev.twitch.com/seeingblue/32/1876_2.png) [@SeeingBlue](https://staging-discuss.dev.twitch.com/u/SeeingBlue)\ **Post date:** [February 17, 2019, 3:22pm UTC](https://staging-discuss.dev.twitch.com/t/helix-sub-missing-count/20045/7 "2019-02-17T15:22:03Z")
Documentation doesn’t show parameters for the cursor. ---
**Author:** ![BarryCarlyon](https://d1d6mrmdu7ztse.cloudfront.net/user_avatar/staging-discuss.dev.twitch.com/barrycarlyon/32/253_2.png) [@BarryCarlyon](https://staging-discuss.dev.twitch.com/u/BarryCarlyon)\ **Post date:** [February 17, 2019, 3:33pm UTC](https://staging-discuss.dev.twitch.com/t/helix-sub-missing-count/20045/8 "2019-02-17T15:33:00Z")
cursor usage is “standard” across all helix endpoints ---
**Author:** ![SeeingBlue](https://d1d6mrmdu7ztse.cloudfront.net/user_avatar/staging-discuss.dev.twitch.com/seeingblue/32/1876_2.png) [@SeeingBlue](https://staging-discuss.dev.twitch.com/u/SeeingBlue)\ **Post date:** [February 17, 2019, 4:44pm UTC](https://staging-discuss.dev.twitch.com/t/helix-sub-missing-count/20045/9 "2019-02-17T16:44:56Z")
Right, I understand that. My point is the documentation is not consistent across all helix endpoints. Either make an overall persistent parameter category the covers all endpoints, or list all the parameters for each endpoint. Otherwise it creates confusion for newcomers, which results in more threads filled with the same questions over and over. ---
**Author:** ![system](https://d2spem0quai2ol.cloudfront.net/original/2X/0/05909729875cce3b53e59d5561c4d23bb14948fc.png) [@system](https://staging-discuss.dev.twitch.com/u/system)\ **Post date:** [March 19, 2019, 4:44pm UTC](https://staging-discuss.dev.twitch.com/t/helix-sub-missing-count/20045/10 "2019-03-19T16:44:59Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.