Stream Search API not returning results

[BrianSipple]

I haven't been able to test the full API completely, so I don't know this issue's full breadth, but it appears that the Search API is currently broken for streams. The example listed directly in the docs...

https://api.twitch.tv/kraken/search/streams?q=starcraft

... returns an empty result array.

Channel search appears to be fine, as does games search, but I have an app that depends on using the stream search and every query that worked last night is now returning no results.

[ghost]

@BrianSipple You should use the full game name, but /search/streams is not a valid url.

You want /channels?q=starcraft

If you want live channels, use
https://api.twitch.tv/kraken/streams?game=StarCraft+II%3A+Heart+of+the+Swarm

[BrianSipple]

Okay, that works... but the example I pasted was directly from the current example in the docs

[ghost]

Yep, that looks broken :P

Potential workaround:

https://api.twitch.tv/kraken/search/games?q=starcraft&type=suggest&live=true

This is probably related:
#398 (comment)

[BrianSipple]

I'm seeing results again with the original example I posted. However, the some of the queries I was using previously don't appear to be returning identical results when the "limit" parameter is used.

For example, try https://api.twitch.tv/kraken/search/streams?q=starcraft&limit=6. It returns a results object that reports 170 total items and provides the necessary links for future api calls. However, the "streams" array that would normally hold 6 results after the first call only holds 4. Future requests with the provided links seem to return a similarly truncated "streams" array as well.

[cgwic]

currenly

get https://api.twitch.tv/kraken/search/streams?q=starcraft&limit=6

returns six for me

[BrianSipple]

Nice -- same here now. As far as I can tell, everything is back to normal with /search/streams?although it might still be worth keeping this issue open for a bit. If whatever caused this was also related to #398, others might be experiencing similar quirks with different varieties of the query.

[Pyyric]

I don't think /search/streams is returning top results anymore. Just calling it raw and searching for streams in the twitch.tv/directory it doesn't find them. Didn't it used to display 25 results by default and then show top viewers first? Ugh, it used to just work and I don't remember what the defaults were.

[BrianSipple]

I've been using the queried route for some time now without noticing any particular issues. Seeing as though there haven't been any more identical cases mentioned here or linked elsewhere, I'm going to go ahead and close this.

[burakkurkcu]

This problem seems to exist still.

With _total parameter response shows there is ~100 streams as I search now, which is much more than I need to limit.

https://api.twitch.tv/kraken/search/streams?q=starcraft&limit=6 returns 6 streams.
https://api.twitch.tv/kraken/search/streams?q=starcraft&limit=7 returns 6 streams.
https://api.twitch.tv/kraken/search/streams?q=starcraft&limit=12 returns 9 streams.
https://api.twitch.tv/kraken/search/streams?q=starcraft&limit=16 returns 14 streams.
https://api.twitch.tv/kraken/search/streams?q=starcraft&limit=18 returns 16 streams.

I only managed to get the correct count of streams as a response to limit <= 6.