# Streams API. Several users streaming-status in a single request

**URL:** <https://discuss.dev.twitch.com/t/streams-api-several-users-streaming-status-in-a-single-request/660>\
**Category:** API\
**Created:** [April 11, 2014, 5:01am UTC](https://discuss.dev.twitch.com/t/streams-api-several-users-streaming-status-in-a-single-request/660 "2014-04-11T05:01:08Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![girlsstreamgame](https://d3ovvz0v2ajtpu.cloudfront.net/user_avatar/discuss.dev.twitch.com/girlsstreamgame/32/189_2.png) [@girlsstreamgame](https://discuss.dev.twitch.com/u/girlsstreamgame)\
**Post date:** [April 11, 2014, 5:01am UTC](https://discuss.dev.twitch.com/t/streams-api-several-users-streaming-status-in-a-single-request/660/1 "2014-04-11T05:01:08Z")

</div>

Hello everyone.  
This is my 1st post, so there can be an answer, if so - you can just give me the link.

The problem is:  
I have several (about 100) accounts I’m tracking in my application. And I want to get status on that accounts for every user that uses my app.  
Currently to get if any of those 100 users is streaming I have to make 1 request per user to twitch api like this: [https://api.twitch.tv/kraken/streams/{username}](https://api.twitch.tv/kraken/streams/%7Busername%7D) after that I’m looking for “stream” node in response and get information from it (stream-screenshot, viewers number etc)

Important thing: I’m not making any of those request on my backend server all is implemented at client side (no caching for now)

I wonder if there any **single** request for that purpose that I can pass list of ids or screen-names  
Something like this maybe: /kraken/streams?users=username1,username2,…

Thanks in advance

UPDATE 1: **/search/streams** didn’t work well for me  
I tried this one: [https://github.com/justintv/Twitch-API/blob/master/v2\_resources/search.md#get-searchstreams](https://github.com/justintv/Twitch-API/blob/master/v2_resources/search.md#get-searchstreams)  
passing **q** parameter as _username1 OR username2 OR username3 …_ but it doesn’t give me the same result as 100 separate requests. Also tried different portions of accounts (15, 25, 50 in a single request) combining with **limit** parameter. Didn’t work

---

<div class="post-metadata">

**Author:** ![Sunspots](https://d3ovvz0v2ajtpu.cloudfront.net/user_avatar/discuss.dev.twitch.com/sunspots/32/1835_2.png) [@Sunspots](https://discuss.dev.twitch.com/u/Sunspots)\
**Post date:** [April 11, 2014, 2:33pm UTC](https://discuss.dev.twitch.com/t/streams-api-several-users-streaming-status-in-a-single-request/660/2 "2014-04-11T14:33:38Z")

</div>

/streams/ will take a channels parameter, like this:

[https://api.twitch.tv/kraken/streams?channel=trick2g,beyondthesummit2,starladder1](https://api.twitch.tv/kraken/streams?channel=trick2g,beyondthesummit2,starladder1)

It returns one stream object for each active stream. There was someone experiencing some issues when requesting a high number of channels, I believe there is a cap to how many you can put in at once(50, 100 maybe?). To take care of that, you could split up the list into multiple requests.

---

<div class="post-metadata">

**Author:** ![girlsstreamgame](https://d3ovvz0v2ajtpu.cloudfront.net/user_avatar/discuss.dev.twitch.com/girlsstreamgame/32/189_2.png) [@girlsstreamgame](https://discuss.dev.twitch.com/u/girlsstreamgame)\
**Post date:** [April 11, 2014, 3:37pm UTC](https://discuss.dev.twitch.com/t/streams-api-several-users-streaming-status-in-a-single-request/660/3 "2014-04-11T15:37:17Z")

</div>

Thank you so much. It looks like it’s working!

---

<div class="post-metadata">

**Author:** ![demonshalo](https://avatars.discourse-cdn.com/v4/letter/d/df705f/32.png) [@demonshalo](https://discuss.dev.twitch.com/u/demonshalo)\
**Post date:** [April 13, 2014, 2:32pm UTC](https://discuss.dev.twitch.com/t/streams-api-several-users-streaming-status-in-a-single-request/660/4 "2014-04-13T14:32:59Z")

</div>

I think that the number of streams you can include depends on the URL length. Some servers cannot handle URLs beyond a certain number of characters.
