# Is it possible to define Tier's level of Subscriber (1, 2, 3) in Twitch Extension (by Twitch API)?

**URL:** <https://discuss.dev.twitch.com/t/is-it-possible-to-define-tiers-level-of-subscriber-1-2-3-in-twitch-extension-by-twitch-api/17457>\
**Category:** Extensions\
**Created:** [August 31, 2018, 11:47am UTC](https://discuss.dev.twitch.com/t/is-it-possible-to-define-tiers-level-of-subscriber-1-2-3-in-twitch-extension-by-twitch-api/17457 "2018-08-31T11:47:14Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![Andy\_Andy](https://avatars.discourse-cdn.com/v4/letter/a/a8b319/32.png) [@Andy\_Andy](https://discuss.dev.twitch.com/u/Andy_Andy)\
**Post date:** [August 31, 2018, 11:47am UTC](https://discuss.dev.twitch.com/t/is-it-possible-to-define-tiers-level-of-subscriber-1-2-3-in-twitch-extension-by-twitch-api/17457/1 "2018-08-31T11:47:14Z")

</div>

Is it possible to define Tier’s level of Subscriber (1, 2, 3) in Twitch Extension (by Twitch API)?

---

<div class="post-metadata">

**Author:** ![BarryCarlyon](https://d3ovvz0v2ajtpu.cloudfront.net/user_avatar/discuss.dev.twitch.com/barrycarlyon/32/253_2.png) [@BarryCarlyon](https://discuss.dev.twitch.com/u/BarryCarlyon)\
**Post date:** [August 31, 2018, 12:54pm UTC](https://discuss.dev.twitch.com/t/is-it-possible-to-define-tiers-level-of-subscriber-1-2-3-in-twitch-extension-by-twitch-api/17457/2 "2018-08-31T12:54:49Z")

</div>

The tier level of what?

I am very unclear to what you mean or are attempting to achieve?

---

<div class="post-metadata">

**Author:** ![Andy\_Andy](https://avatars.discourse-cdn.com/v4/letter/a/a8b319/32.png) [@Andy\_Andy](https://discuss.dev.twitch.com/u/Andy_Andy)\
**Post date:** [August 31, 2018, 12:57pm UTC](https://discuss.dev.twitch.com/t/is-it-possible-to-define-tiers-level-of-subscriber-1-2-3-in-twitch-extension-by-twitch-api/17457/3 "2018-08-31T12:57:20Z")

</div>

Sorry, I mean tier level of subscriber.

---

<div class="post-metadata">

**Author:** ![BarryCarlyon](https://d3ovvz0v2ajtpu.cloudfront.net/user_avatar/discuss.dev.twitch.com/barrycarlyon/32/253_2.png) [@BarryCarlyon](https://discuss.dev.twitch.com/u/BarryCarlyon)\
**Post date:** [August 31, 2018, 6:04pm UTC](https://discuss.dev.twitch.com/t/is-it-possible-to-define-tiers-level-of-subscriber-1-2-3-in-twitch-extension-by-twitch-api/17457/4 "2018-08-31T18:04:10Z")

</div>

In an extension:

You cannot request oAuth scopes from a user/viewer

You can request oAuth scopes from the broadcaster/channel the extension is installed/in user upon via the config panel. Which will then grant you access to their sub list as documented here:

> **[Reference](https://dev.twitch.tv/docs/api/reference/)**
>
> Twitch Developer tools and services to integrate Twitch into your development or create interactive experience on twitch.tv.

---

<div class="post-metadata">

**Author:** ![Andy\_Andy](https://avatars.discourse-cdn.com/v4/letter/a/a8b319/32.png) [@Andy\_Andy](https://discuss.dev.twitch.com/u/Andy_Andy)\
**Post date:** [September 3, 2018, 9:57am UTC](https://discuss.dev.twitch.com/t/is-it-possible-to-define-tiers-level-of-subscriber-1-2-3-in-twitch-extension-by-twitch-api/17457/5 "2018-09-03T09:57:16Z")

</div>

Oh cool,  
as I understand this json tell us about money and subscirbe name?

```auto
            "sub_plan": "1000",
            "sub_plan_name": "Channel Subscription (mr_woodchuck)",

```

---

<div class="post-metadata">

**Author:** ![swiftyspiffy](https://d3ovvz0v2ajtpu.cloudfront.net/user_avatar/discuss.dev.twitch.com/swiftyspiffy/32/1279_2.png) [@swiftyspiffy](https://discuss.dev.twitch.com/u/swiftyspiffy)\
**Post date:** [September 3, 2018, 10:11am UTC](https://discuss.dev.twitch.com/t/is-it-possible-to-define-tiers-level-of-subscriber-1-2-3-in-twitch-extension-by-twitch-api/17457/6 "2018-09-03T10:11:21Z")

</div>

More or less. Be careful about assuming that `sub_plan` 1000, 2000, 3000 maps to $4.99, $9.99, and $24.99, that isn’t always the case.  
You also shouldn’t assume anything about the `sub_plan_name`. There are other fields in the payload that more explicitly tell you what you’re looking for.

---

<div class="post-metadata">

**Author:** ![Andy\_Andy](https://avatars.discourse-cdn.com/v4/letter/a/a8b319/32.png) [@Andy\_Andy](https://discuss.dev.twitch.com/u/Andy_Andy)\
**Post date:** [September 3, 2018, 10:45am UTC](https://discuss.dev.twitch.com/t/is-it-possible-to-define-tiers-level-of-subscriber-1-2-3-in-twitch-extension-by-twitch-api/17457/7 "2018-09-03T10:45:18Z")

</div>

I can’t find more exact field…

---

<div class="post-metadata">

**Author:** ![swiftyspiffy](https://d3ovvz0v2ajtpu.cloudfront.net/user_avatar/discuss.dev.twitch.com/swiftyspiffy/32/1279_2.png) [@swiftyspiffy](https://discuss.dev.twitch.com/u/swiftyspiffy)\
**Post date:** [September 3, 2018, 10:33pm UTC](https://discuss.dev.twitch.com/t/is-it-possible-to-define-tiers-level-of-subscriber-1-2-3-in-twitch-extension-by-twitch-api/17457/8 "2018-09-03T22:33:44Z")

</div>

I was referring to the subscriber name. The name should be in the payload. Additionally, you can use the 1000,2000,3000, but my point was that you shouldn’t assume static values on the pricing as there are a few channels that deviate from it.

---

<div class="post-metadata">

**Author:** ![Andy\_Andy](https://avatars.discourse-cdn.com/v4/letter/a/a8b319/32.png) [@Andy\_Andy](https://discuss.dev.twitch.com/u/Andy_Andy)\
**Post date:** [September 4, 2018, 8:49am UTC](https://discuss.dev.twitch.com/t/is-it-possible-to-define-tiers-level-of-subscriber-1-2-3-in-twitch-extension-by-twitch-api/17457/9 "2018-09-04T08:49:17Z")

</div>

Ok, I understand you @swiftyspiffy good point, thank you!
