Four hours ago, Twitch changed the "limit=" parameter on the "streams" endpoints and broke my app. Is this permanent?

[Praxis]

Hello- four hours ago, the “limit=” modifier was changed to limit the query from selecting a limit between 1 and 100.

For example:
https://api.twitch.tv/kraken/streams?game=Super+Smash+Bros.&limit=150
is broken and returns:
{“error”:“Bad Request”,“status”:400,“message”:“The parameter “limit” was malformed: the value must be less than or equal to 100”}

But:
https://api.twitch.tv/kraken/search/channels?q=starcraft&limit=150
returns data.

My app was using “limit=150” and is now broken. Does Twitch intend to continue enforcing this new limitation? (I want to verify before I go through the trouble of rebuilding new versions of my app and submitting them through the app store approval process and wiping out my current reviews in the process, meanwhile having up to a week of downtime for my users.)

[3ventic]

Did it actually return 150? As far as I know it allowed you to specify a limit higher than 100 but would only return 100.

[Kiskae]

The maximum has been 100 since 2013: https://github.com/justintv/Twitch-API/blob/master/v3_resources/streams.md#get-streams

I guess they simply added validation so it no longer accepts invalid parameters