# Get multiple channels like you can with streams

**URL:** <https://staging-discuss.dev.twitch.com/t/get-multiple-channels-like-you-can-with-streams/7920>\
**Category:** API\
**Created:** [October 25, 2016, 11:00pm UTC](https://staging-discuss.dev.twitch.com/t/get-multiple-channels-like-you-can-with-streams/7920 "2016-10-25T23:00:03Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![DevUser](https://d1d6mrmdu7ztse.cloudfront.net/user_avatar/staging-discuss.dev.twitch.com/devuser/32/7344_2.png) [@DevUser](https://staging-discuss.dev.twitch.com/u/DevUser)\
**Post date:** [October 25, 2016, 11:00pm UTC](https://staging-discuss.dev.twitch.com/t/get-multiple-channels-like-you-can-with-streams/7920/1 "2016-10-25T23:00:03Z")

</div>

Would it be possible to be able to get multiple channels in a single call like you can with streams?

The issue is getting information about multiple channels that are not online. Right now if you want to get info about 10 channels you would have to make 10 separate calls.

---

<div class="post-metadata">

**Author:** ![DallasNChains](https://d1d6mrmdu7ztse.cloudfront.net/user_avatar/staging-discuss.dev.twitch.com/dallasnchains/32/1608_2.png) [@DallasNChains](https://staging-discuss.dev.twitch.com/u/DallasNChains)\
**Post date:** [October 26, 2016, 12:05am UTC](https://staging-discuss.dev.twitch.com/t/get-multiple-channels-like-you-can-with-streams/7920/2 "2016-10-26T00:05:05Z")

</div>

> [@Still no API for multiple channels?](https://staging-discuss.dev.twitch.com/t/still-no-api-for-multiple-channels/7339):
>
> I basically have the same question as [Query multiple channels in 1 call?](https://staging-discuss.dev.twitch.com/t/query-multiple-channels-in-1-call/4031) , but as it’s been a year, I thought I’d check whether it’s still true that this doesn’t exist. I’m here because of [https://www.freecodecamp.com/challenges/use-the-twitchtv-json-api](https://www.freecodecamp.com/challenges/use-the-twitchtv-json-api) , and for that application it would be great to have one call that gets you all the channels’ names, logos, and statuses, whether online or not; seems to make more sense than one streams/?channel call to catch the online ones, and then a separat…

---

<div class="post-metadata">

**Author:** ![DevUser](https://d1d6mrmdu7ztse.cloudfront.net/user_avatar/staging-discuss.dev.twitch.com/devuser/32/7344_2.png) [@DevUser](https://staging-discuss.dev.twitch.com/u/DevUser)\
**Post date:** [October 26, 2016, 3:50am UTC](https://staging-discuss.dev.twitch.com/t/get-multiple-channels-like-you-can-with-streams/7920/3 "2016-10-26T03:50:24Z")

</div>

I don’t understand the reasoning in the post. I can do this just fine with the current API it just takes a long time because I have to do a separate a request for each channel.

---

<div class="post-metadata">

**Author:** ![3ventic](https://d1d6mrmdu7ztse.cloudfront.net/user_avatar/staging-discuss.dev.twitch.com/3ventic/32/298_2.png) [@3ventic](https://staging-discuss.dev.twitch.com/u/3ventic)\
**Post date:** [October 26, 2016, 4:38am UTC](https://staging-discuss.dev.twitch.com/t/get-multiple-channels-like-you-can-with-streams/7920/4 "2016-10-26T04:38:48Z")

</div>

Additional requests don’t cause that much overhead or even take very long if you reuse the connections between requests.

---

<div class="post-metadata">

**Author:** ![DevUser](https://d1d6mrmdu7ztse.cloudfront.net/user_avatar/staging-discuss.dev.twitch.com/devuser/32/7344_2.png) [@DevUser](https://staging-discuss.dev.twitch.com/u/DevUser)\
**Post date:** [October 26, 2016, 5:23am UTC](https://staging-discuss.dev.twitch.com/t/get-multiple-channels-like-you-can-with-streams/7920/5 "2016-10-26T05:23:56Z")

</div>

Yes, that’s my point. There are many way you can achieve this already so why not just have it in the API for convenience?

---

<div class="post-metadata">

**Author:** ![3ventic](https://d1d6mrmdu7ztse.cloudfront.net/user_avatar/staging-discuss.dev.twitch.com/3ventic/32/298_2.png) [@3ventic](https://staging-discuss.dev.twitch.com/u/3ventic)\
**Post date:** [October 26, 2016, 3:16pm UTC](https://staging-discuss.dev.twitch.com/t/get-multiple-channels-like-you-can-with-streams/7920/6 "2016-10-26T15:16:43Z")

</div>

I don’t know how the API backend works exactly, but single channel json can be cached as a whole while a reply with multiple channels would have to be constructed specifically for each request.

---

<div class="post-metadata">

**Author:** ![DevUser](https://d1d6mrmdu7ztse.cloudfront.net/user_avatar/staging-discuss.dev.twitch.com/devuser/32/7344_2.png) [@DevUser](https://staging-discuss.dev.twitch.com/u/DevUser)\
**Post date:** [October 27, 2016, 5:38pm UTC](https://staging-discuss.dev.twitch.com/t/get-multiple-channels-like-you-can-with-streams/7920/7 "2016-10-27T17:38:27Z")

</div>

Can’t you just send multiple cached channels as a single response?

---

<div class="post-metadata">

**Author:** ![3ventic](https://d1d6mrmdu7ztse.cloudfront.net/user_avatar/staging-discuss.dev.twitch.com/3ventic/32/298_2.png) [@3ventic](https://staging-discuss.dev.twitch.com/u/3ventic)\
**Post date:** [October 27, 2016, 6:04pm UTC](https://staging-discuss.dev.twitch.com/t/get-multiple-channels-like-you-can-with-streams/7920/8 "2016-10-27T18:04:46Z")

</div>

You can, but the json needs to be constructed specifically for the request from the cached pieces.

---

<div class="post-metadata">

**Author:** ![system](https://d2spem0quai2ol.cloudfront.net/original/2X/0/05909729875cce3b53e59d5561c4d23bb14948fc.png) [@system](https://staging-discuss.dev.twitch.com/u/system)\
**Post date:** [November 26, 2016, 6:04pm UTC](https://staging-discuss.dev.twitch.com/t/get-multiple-channels-like-you-can-with-streams/7920/9 "2016-11-26T18:04:49Z")

</div>

Closed on November 26, 2016, 6:04pm UTC

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