# User ID -\> Username Retrieval **URL:** \ **Category:** Extensions\ **Created:** [September 11, 2017, 2:39am UTC](https://staging-discuss.dev.twitch.com/t/user-id-username-retrieval/11905 "2017-09-11T02:39:15Z")\ **Posts on this page:** 2\ **Page:** 2
**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:** [January 31, 2021, 7:25pm UTC](https://staging-discuss.dev.twitch.com/t/user-id-username-retrieval/11905/21 "2021-01-31T19:25:29Z")
1. You necored a 3 years old post (please don’t do this) 2. Kraken is deprecated and will be removed soon ™ 3. Use of kraken is discoured and developers should move to Helix 4. Yes all helix requests require a token for server to server calls use an app access token/client credentials [https://dev.twitch.tv/docs/authentication/getting-tokens-oauth#oauth-client-credentials-flow](https://dev.twitch.tv/docs/authentication/getting-tokens-oauth#oauth-client-credentials-flow) 5. This post pertains to extensions, it is unwise to use kraken in extensions due to the above mentioned issues, and such an extension likely won’t pass review (when making kraken calls in the frontend). This example more accurately covers OP’s original use case [https://github.com/BarryCarlyon/twitch\_profile\_extension](https://github.com/BarryCarlyon/twitch_profile_extension) ---
**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:** [January 31, 2021, 7:27pm UTC](https://staging-discuss.dev.twitch.com/t/user-id-username-retrieval/11905/22 "2021-01-31T19:27:08Z")
[Previous page](https://staging-discuss.dev.twitch.com/t/user-id-username-retrieval/11905.md?page=1)