Consider the following
Fetch: https://api.twitch.tv/kraken/channels/cohhcarnage/follows?limit=100
The _total key element says we have 239315 followers (at time of writing)
The last page in theory is about https://api.twitch.tv/kraken/channels/cohhcarnage/follows?limit=100&offset=239300
The result message is:
{“error”:“Forbidden”,“status”:403,“message”:“Offset too high”}
So, something appears to have exploded…
Also to reopen Followers End Point Bug? if you were to iterate thru all “pages” the _total would sometimes be blank/0 if you were to iterate quickly, but I’ve not confirmed this recently.
I’ve just got to $dayjob so I can’t debug further at this time, to see where the “fetch all followers” script is failing.
It’s my “fetch quick” script that is failing (which starts from the last page and works back), my slow script is running and will report back/has run, it failed at an offset of 1700
With the same error, URL https://api.twitch.tv/kraken/channels/cohhcarnage/follows?direction=DESC&limit=100&offset=1700 same JSON response, Forbidden, 403, offset too high.
I checked another channel: https://api.twitch.tv/kraken/channels/dethridgecraft/follows?direction=DESC&limit=100&offset=1700 same issue.
I’m also seeing some cases where the same user appears on multiple pages (which I deal with internally), I also see this on the Subscribers of a channel endpoint (which I also deal with internally)
(And can be please allow a larger limit on the followers end point?)