# 'user\_name' in Get Stream response sometimes cannot be used as 'channel' to play in the embedded player

**URL:** <https://discuss.dev.twitch.com/t/user-name-in-get-stream-response-sometimes-cannot-be-used-as-channel-to-play-in-the-embedded-player/26016>\
**Category:** API\
**Created:** [May 30, 2020, 7:06am UTC](https://discuss.dev.twitch.com/t/user-name-in-get-stream-response-sometimes-cannot-be-used-as-channel-to-play-in-the-embedded-player/26016 "2020-05-30T07:06:54Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![watchitlive](https://d3ovvz0v2ajtpu.cloudfront.net/user_avatar/discuss.dev.twitch.com/watchitlive/32/8072_2.png) [@watchitlive](https://discuss.dev.twitch.com/u/watchitlive)\
**Post date:** [May 30, 2020, 7:06am UTC](https://discuss.dev.twitch.com/t/user-name-in-get-stream-response-sometimes-cannot-be-used-as-channel-to-play-in-the-embedded-player/26016/1 "2020-05-30T07:06:54Z")

</div>

I noticed this live stream today has a user\_name “Riot Games”. When I use it as ‘channel’ in the embedded player, it wouldn’t play. “RiotGames” without the space works. Maybe this specific case is a bug? Or we should reference something else as the ‘channel’. Please advise. Thanks.  
{  
“id”: “38366429088”,  
“user\_id”: “36029255”,  
“user\_name”: “Riot Games”,  
“game\_id”: “21779”,  
“type”: “live”,  
“title”: “Mid-Season Streamathon: LPL vs LCK Mid-Season Cup Semifinals”,  
“viewer\_count”: 43920,  
“started\_at”: “2020-05-29T23:02:15Z”,  
“language”: “en”,  
“thumbnail\_url”: “[https://static-cdn.jtvnw.net/previews-ttv/live\_user\_riotgames-{width}x{height}.jpg](https://static-cdn.jtvnw.net/previews-ttv/live_user_riotgames-%7Bwidth%7Dx%7Bheight%7D.jpg)”,  
“tag\_ids”: [  
“36a89a80-4fcd-4b74-b3d2-2c6fd9b30c95”,  
“6ea6bca4-4712-4ab9-a906-e3336a9d8039”  
]  
},

(p.s. as a temporary workaround, I’m skipping all the spaces)

---

<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:** [May 30, 2020, 11:24am UTC](https://discuss.dev.twitch.com/t/user-name-in-get-stream-response-sometimes-cannot-be-used-as-channel-to-play-in-the-embedded-player/26016/2 "2020-05-30T11:24:29Z")

</div>

> <https://github.com/twitchdev/issues/issues/3>
>
> \*\*Brief description\*\*
> 
> Streams API returns the \`user\_name\` as the users \`displ…ay\_name\` instead.
> 
> Meaning for people building a embed from an API lookup either parse the thumbnail URL for the username, or call the users API to get the correct login name for the embed.
> 
> This is particularly a problem for "Korean" Streamers
> 
> For example
> 
> https://api.twitch.tv/helix/streams?user\_id=139470326
> 
> Which returns the user\_name as \`한동숙\` which is not valid for building a embed or channel URL
> 
> \*\*How to reproduce\*\*
> 
> Call https://api.twitch.tv/helix/streams?user\_login=cohhcarnage
> 
> \*\*Expected behavior\*\*
> 
> Return "cohhcarnage" as the user\_name instead of "CohhCarnage"
> 
> And/or extend the endpoint to return both

---

<div class="post-metadata">

**Author:** ![watchitlive](https://d3ovvz0v2ajtpu.cloudfront.net/user_avatar/discuss.dev.twitch.com/watchitlive/32/8072_2.png) [@watchitlive](https://discuss.dev.twitch.com/u/watchitlive)\
**Post date:** [May 31, 2020, 6:35am UTC](https://discuss.dev.twitch.com/t/user-name-in-get-stream-response-sometimes-cannot-be-used-as-channel-to-play-in-the-embedded-player/26016/3 "2020-05-31T06:35:13Z")

</div>

Thanks Barry -

---

<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:** [June 30, 2020, 6:35am UTC](https://discuss.dev.twitch.com/t/user-name-in-get-stream-response-sometimes-cannot-be-used-as-channel-to-play-in-the-embedded-player/26016/4 "2020-06-30T06:35:52Z")

</div>

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