# Helix - Get Broadcaster Subscriptions only returning 20

**URL:** <https://staging-discuss.dev.twitch.com/t/helix-get-broadcaster-subscriptions-only-returning-20/22833>\
**Category:** API\
**Created:** [October 14, 2019, 5:01pm UTC](https://staging-discuss.dev.twitch.com/t/helix-get-broadcaster-subscriptions-only-returning-20/22833 "2019-10-14T17:01:58Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sonny\_D](https://d1d6mrmdu7ztse.cloudfront.net/user_avatar/staging-discuss.dev.twitch.com/sonny_d/32/7219_2.png) [@Sonny\_D](https://staging-discuss.dev.twitch.com/u/Sonny_D)\
**Post date:** [October 14, 2019, 5:01pm UTC](https://staging-discuss.dev.twitch.com/t/helix-get-broadcaster-subscriptions-only-returning-20/22833/1 "2019-10-14T17:01:58Z")

</div>

I came across a problem today while migrating vom V5 to new twitch api.

When using: [https://api.twitch.tv/helix/subscriptions?broadcaster\_id=](https://api.twitch.tv/helix/subscriptions?broadcaster_id=) where is an actual ID, the request only returns 20 subs.

I’ve also added &limit=100 and tried with &offset but nothing works. It only shows up 20 subs. This is just not correct. I’m even missing some gifted subs.

When using the old api, the sub count is correct with 36 subs showing up on test account (which is the correct number).

There are subs missing with helix.  
Am I missing something? Or is this an actual bug?

---

<div class="post-metadata">

**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:** [October 14, 2019, 5:10pm UTC](https://staging-discuss.dev.twitch.com/t/helix-get-broadcaster-subscriptions-only-returning-20/22833/2 "2019-10-14T17:10:43Z")

</div>

Helix doesn’t use the `limit` or `offset` params.

If you want to adjust how many results are returned you use the `first` param, eg `&first=100`

If you have more results that shown you need to use pagination, this can be done by looking at the cursor provided in the response and using that as the `after` param, which will all you to retrieve the next page of results (and a new cursor if there are more pages).

---

<div class="post-metadata">

**Author:** ![Sonny\_D](https://d1d6mrmdu7ztse.cloudfront.net/user_avatar/staging-discuss.dev.twitch.com/sonny_d/32/7219_2.png) [@Sonny\_D](https://staging-discuss.dev.twitch.com/u/Sonny_D)\
**Post date:** [October 14, 2019, 5:11pm UTC](https://staging-discuss.dev.twitch.com/t/helix-get-broadcaster-subscriptions-only-returning-20/22833/3 "2019-10-14T17:11:35Z")

</div>

Awesome, thank you very very much! Is this in API Docs already and i’ve missed it?

---

<div class="post-metadata">

**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:** [October 14, 2019, 5:14pm UTC](https://staging-discuss.dev.twitch.com/t/helix-get-broadcaster-subscriptions-only-returning-20/22833/4 "2019-10-14T17:14:27Z")

</div>

The docs for Get Broadcaster Subscriptions [https://dev.twitch.tv/docs/api/reference#get-broadcaster-subscriptions](https://dev.twitch.tv/docs/api/reference#get-broadcaster-subscriptions) are very badly written, but if you look at any of the other API references for Helix you’ll see what are/aren’t available params, as well as how to use them such as the `after` param, and the inclusion of cursors in example responses.

---

<div class="post-metadata">

**Author:** ![system](https://d2spem0quai2ol.cloudfront.net/original/2X/0/05909729875cce3b53e59d5561c4d23bb14948fc.png) [@system](https://staging-discuss.dev.twitch.com/u/system)\
**Post date:** [November 13, 2019, 5:14pm UTC](https://staging-discuss.dev.twitch.com/t/helix-get-broadcaster-subscriptions-only-returning-20/22833/5 "2019-11-13T17:14:30Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.