# Question about OAuth Access for the new Helix API

**URL:** <https://discuss.dev.twitch.com/t/question-about-oauth-access-for-the-new-helix-api/13526>\
**Category:** API\
**Created:** [January 5, 2018, 2:15am UTC](https://discuss.dev.twitch.com/t/question-about-oauth-access-for-the-new-helix-api/13526 "2018-01-05T02:15:46Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![DManstrator](https://d3ovvz0v2ajtpu.cloudfront.net/user_avatar/discuss.dev.twitch.com/dmanstrator/32/3918_2.png) [@DManstrator](https://discuss.dev.twitch.com/u/DManstrator)\
**Post date:** [January 5, 2018, 2:15am UTC](https://discuss.dev.twitch.com/t/question-about-oauth-access-for-the-new-helix-api/13526/1 "2018-01-05T02:15:47Z")

</div>

Hey,

today I started programming with the Twitch API and thankfully I saw, that Kraken gets outdated in the end of this year and that developers should use the new Helix Version.

I worked a bit with Kraken, was able to get access to and find the values that I need from the API, but now with Helix, I neither get access nor can I find the data I want to use.

For Authorization, I used OAuth Implicit Code Flow and in the Helix Documentation it states, that this is still working now. But when I use the OAuth Token I get via. `https://api.twitch.tv/kraken/oauth2/authorize?client_id=<<clientId>&redirect_uri=http://localhost&response_type=token`, it says it is not valid. Do I really have to “manipulate” the request header? And why kraken, when it’ll get removed “soon”?

Another little question would be where to update the user game or title? I just found how to change the description of a user.  
In the V5-API, it was shown: [https://dev.twitch.tv/docs/v5/reference/channels#update-channel](https://dev.twitch.tv/docs/v5/reference/channels#update-channel)  
What value for Accept would be necessary to make it work? (I guess the Authorize Value is `Authorization: Bearer <access token>`.)

Kind regards,

DMan

---

<div class="post-metadata">

**Author:** ![Six](https://d3ovvz0v2ajtpu.cloudfront.net/user_avatar/discuss.dev.twitch.com/six/32/2334_2.png) [@Six](https://discuss.dev.twitch.com/u/Six)\
**Post date:** [January 5, 2018, 2:23pm UTC](https://discuss.dev.twitch.com/t/question-about-oauth-access-for-the-new-helix-api/13526/2 "2018-01-05T14:23:27Z")

</div>

> [@DManstrator](#):
>
> And why kraken, when it’ll get removed “soon”?

Helix uses the same types of tokens as Kraken, so they just reused the same endpoint.

> [@DManstrator](#):
>
> Another little question would be where to update the user game or title?

As of now, only the description can be updated via Helix.

> [@DManstrator](#):
>
> What value for Accept would be necessary to make it work?

With helix, you no longer need to set `Accept` headers. All you have to do is attach the necessary tokens/client-id’s and make the request like normal.

---

<div class="post-metadata">

**Author:** ![DManstrator](https://d3ovvz0v2ajtpu.cloudfront.net/user_avatar/discuss.dev.twitch.com/dmanstrator/32/3918_2.png) [@DManstrator](https://discuss.dev.twitch.com/u/DManstrator)\
**Post date:** [January 6, 2018, 1:15am UTC](https://discuss.dev.twitch.com/t/question-about-oauth-access-for-the-new-helix-api/13526/3 "2018-01-06T01:15:18Z")

</div>

> [@Six](#):
>
> As of now, only the description can be updated via Helix.

So the new API isn’t complete, yet? Why was the API released then when it might change a lot until it’s complete?

> [@DManstrator](#):
>
> Do I really have to “manipulate” the request header?

I did that for now even it is kinda inconvenient (sending a simple request over the Browser is easier). Really not possible in the old way?

---

<div class="post-metadata">

**Author:** ![3ventic](https://d3ovvz0v2ajtpu.cloudfront.net/user_avatar/discuss.dev.twitch.com/3ventic/32/298_2.png) [@3ventic](https://discuss.dev.twitch.com/u/3ventic)\
**Post date:** [January 6, 2018, 3:03am UTC](https://discuss.dev.twitch.com/t/question-about-oauth-access-for-the-new-helix-api/13526/4 "2018-01-06T03:03:45Z")

</div>

> [@DManstrator](#):
>
> So the new API isn’t complete, yet? Why was the API released then when it might change a lot until it’s complete?

As far as I know, the goal is to add to the API, but not change what’s once been added.

---

<div class="post-metadata">

**Author:** ![system](https://d2opxh93rbxzdn.cloudfront.net/original/2X/0/05909729875cce3b53e59d5561c4d23bb14948fc.png) [@system](https://discuss.dev.twitch.com/u/system)\
**Post date:** [February 5, 2018, 3:04am UTC](https://discuss.dev.twitch.com/t/question-about-oauth-access-for-the-new-helix-api/13526/5 "2018-02-05T03:04:03Z")

</div>

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