{
"error": "Gone",
"status": 410,
"message": "War. War never changes... but APIs do. See https://dev.twitch.tv/docs"
}
periodically, not always. v5 headers, not v3.
{
"error": "Gone",
"status": 410,
"message": "War. War never changes... but APIs do. See https://dev.twitch.tv/docs"
}
periodically, not always. v5 headers, not v3.
Do you have logs of your request when youāre getting a 410 error? because if youāre using the v5 header you shouldnāt get that response
Iām, intermittently, getting the same
I call https://api.twitch.tv/kraken/games/top?limit=100 every 5 minutes
with headers āClient-IDā: MY_CLIENT_ID, āAcceptā: āapplication/vnd.twitchtv.v5+jsonā
410 was returned at 2019-10-15 02:40:00 UTC
Edit (times are UTC):
2019-10-15 03:05:01: 200
2019-10-15 03:10:01: 200
2019-10-15 03:15:01: 410
2019-10-15 03:20:01: 200
2019-10-15 03:25:01: 200
2019-10-15 03:30:01: 200
2019-10-15 03:35:01: 200
2019-10-15 03:40:01: 200
2019-10-15 03:45:01: 200
2019-10-15 03:50:01: 200
2019-10-15 03:55:01: 410
2019-10-15 04:00:01: 200
2019-10-15 04:05:01: 200
2019-10-15 04:10:01: 200
2019-10-15 04:15:01: 410
2019-10-15 04:20:01: 200
Edit2:
I modified my code to retry (once) if a 410 is returned.
This gave:
2019-10-15 04:25:01: 200
2019-10-15 04:30:01: 200
2019-10-15 04:35:01: 200
2019-10-15 04:40:01: 200
2019-10-15 04:45:01: 200
2019-10-15 04:50:01: 410
2019-10-15 04:50:01: 410
2019-10-15 04:55:01: 200
2019-10-15 05:00:01: 200
2019-10-15 05:05:01: 200
2019-10-15 05:10:01: 200
2019-10-15 05:15:01: 200
2019-10-15 05:20:01: 410
2019-10-15 05:20:01: 410
2019-10-15 05:25:01: 200
2019-10-15 05:30:01: 200
2019-10-15 05:35:01: 200
2019-10-15 05:40:01: 200
2019-10-15 05:45:01: 410
2019-10-15 05:45:01: 410
2019-10-15 05:50:01: 200
2019-10-15 05:55:01: 200
2019-10-15 06:00:01: 200
2019-10-15 06:05:01: 200
2019-10-15 06:10:01: 410
2019-10-15 06:10:01: 410
2019-10-15 06:15:01: 200
2019-10-15 06:20:01: 410
2019-10-15 06:20:01: 410
2019-10-15 06:25:01: 410
2019-10-15 06:25:01: 410
2019-10-15 06:30:01: 410
2019-10-15 06:30:01: 410
2019-10-15 06:35:01: 200
2019-10-15 06:40:01: 200
2019-10-15 06:45:01: 200
2019-10-15 06:50:01: 200
2019-10-15 06:55:01: 200
2019-10-15 07:00:01: 200
2019-10-15 07:05:01: 410
2019-10-15 07:05:01: 410
2019-10-15 07:10:01: 200
2019-10-15 07:15:01: 410
2019-10-15 07:15:01: 410
Note that, every time 410 is returned, an immediate retry also returns 410
Can confirm some wonky stuff on the 14th/15th. First occurrence on Oct 10th, 11:30 PM UTC.
1:00 AM, 2:00 AM, 8:00 AM, 11:00AM, 7:30 PM, 10:30PM UTC on Oct 14th.
3:00 AM, 4:00 AM, 9:30 AM, 10:00 AM UTC on Oct 15th.
All requests:
"params": {
"limit": 100,
"offset": 0
}
Though you can force a 410 by specifying an offset thatās too large. This behavior however is extremely unusual. I believe it has been a 404 in the past, and of course since itās not a cursored endpoint, thereās no guarantee that while Iām traversing the games, that the total
doesnāt change and I inadvertently wind up calling the endpoint with an offset that is now too large.
I still have this problem.
The problem is that for some devices the problem doesnāt happens, for others only some times one two a day, and for others all the time.
Iām using a workaround that every time it returns 410 I start using helix, but helix is not yet done so the result it returns is not complete as kraken.
So is this be worked on and will eventually be fixed?
Is here on this site that we post api problems so they get fixed?
One canāt open a ticket on the dev support site anymore as the feature was removed so I wonder if posting problem here actually reach those responsible for the api after all this is open for some time and the issue persist.
tl;dr: Add &api_version=5 to your URL
(even if you already have āAcceptā: āapplication/vnd.twitchtv.v5+jsonā in the headers)
The problem appears to be related to the shutdown of v3 APIs, and (sometimes) the v3 version being called, even when āAcceptā: āapplication/vnd.twitchtv.v5+jsonā is in the headers.
So, I tried calling https://api.twitch.tv/kraken/games/top?limit=100&api_version=5 whenever https://api.twitch.tv/kraken/games/top?limit=100 returned 410
Since making this change 2 days ago:
After that change all good, using for days now and no more 410s. Thanks @SPDene for the workaround I didnāt know about thatā¦
I took the time and add api_version=5 to all kraken calls to prevent future problems from any API.
Is Followed Games gone as well?
https://api.twitch.tv/api/users/s0und/follows/games/live?limit=100
This used to work, until today. Iām providing a client-id and application/vnd.twitchtv.v5+json
{
"error": "Gone",
"status": 410,
"message": "this API has been removed."
}
i tried with with an additional &api_version=5
, but the result is the same
Maybe itās my fault, but is there a newer api for the same functionality? I couldnāt find any.
I cannot find an equivalent endpoint for that under
or
So itās a undocumented endpoint from what I can see as it starts https://api.twitch.tv/api/
which is not intended for third parties to use
https://api.twitch.tv/kraken/users/<user-id>/follows/games
As it turn out this api, has a āgamesā controller, which is btw undocumented as well, but it just lists the userās followed games, without the āLive viewer countā data, which is pretty important.
I guess this is not even used by twitch itself since the site uses GraphQL now:
https://api.twitch.tv/api/users/s0und/follows/games/live?limit=100
itās working once againā¦
ĀÆ_(ć)_/ĀÆ
thanks?
https://api.twitch.tv/api/users/<channel>/follows/games/live
was an unsupported endpoint that has been removed.
https://api.twitch.tv/kraken/games/top
however is available in v5 (although deprecated) and should not be returning a 410. I was able to replicate this one and have forwarded the behavior to the team to investigate. The initial response was that there was an internal server error and they are looking into why the 410 was sent instead of a more appropriate error code and message.
Hi folks, a fix was rolled out today for the issue causing unexpected 410s for top games. You should no longer receive these error messages.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.