# Helix Prime Subscriptions

**URL:** <https://staging-discuss.dev.twitch.com/t/helix-prime-subscriptions/13527>\
**Category:** API\
**Created:** [January 5, 2018, 2:31am UTC](https://staging-discuss.dev.twitch.com/t/helix-prime-subscriptions/13527 "2018-01-05T02:31:10Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**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:** [January 5, 2018, 2:31am UTC](https://staging-discuss.dev.twitch.com/t/helix-prime-subscriptions/13527/1 "2018-01-05T02:31:10Z")

</div>

Hello, I’m assuming at some point the channel subscription endpoint will be added to the Helix API??

I am curious if there are plans to allow differentiation between 4.99 and Prime subscription plans when that happens. With the Kraken API, it appears that these 2 sub plans are grouped together as ‘1000’.

@BarryCarlyon made mention they think this is too ‘Secret’ to share with a scoped oauth? Perhaps Twitch/Amazon does not want these numbers revealed? Though they could be gathered parsing IRC for a month publicly, even though people are not supposed to gather information about users…

> [@How do we fetch Twitch Prime subscriptions?](https://staging-discuss.dev.twitch.com/t/how-do-we-fetch-twitch-prime-subscriptions/7719/11):
>
> It’s probably too secret to be in the “open” API even with oauth.

---

<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:** [February 4, 2018, 2:31am UTC](https://staging-discuss.dev.twitch.com/t/helix-prime-subscriptions/13527/2 "2018-02-04T02:31:11Z")

</div>

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