The ‘client_id’ parameter only shows streams from applications of client_id.
[/quote]
I am well aware, but the the previous state of the endpoint also had that parameter, and yet it didn’t break when sending your own client_id like you’re supposed to with every request to the API.
Sending the “client_id” parameter as a http-header with every request is not possible for all browsers and JSONP, thus making this parameter name-crash rather stupid.