Incorrect 'next' and 'previous' links from streams api?

Looks like last night the streams api either changed the ‘next’ and ‘previous’ links to now include ‘channel=’
or leaving the ‘channel’ parameter empty now results in no streams being returned (didn’t pay much attention before, it just worked :wink:

Either way, fetching and following the ‘next’ url will not behave as expected and return 0 streams.

I’ve solved this by just parsing out the ‘channel’ parameter, but though I’d post a warning here.
Or maybe I’m missing something :slight_smile:


Thanks for the report, I’ve passed it to the api team for investigation.

I don’t know if it’s related, but I’ve been getting error 400 from[channel]. Other API requests wich are requested in the same way work fine. When I open it in the browser it works, it must be some difference in the request to my program, but only on that endpoint.

Edit: I solved it. I was sending the Content-Type header even when it was a GET request where it’s not really necessary. That code hasn’t changed in years though, so still, some configuration change on that endpoint must have made it less lenient or something.

A fix was deployed for this issue. Thanks for the report!

Great, thanks for the quick response!

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