Helix API - Top Games 503 HTTP

[HerrAusragend]

When querying the “Top Games API” with a given cursor and a first parameter of 100 I get pretty confusing results. This is a dump of 3 calls issued within 2 seconds:

https://api.twitch.tv/helix/games/top?after=eyJiIjp7Ik9mZnNldCI6MTAyOH0sImEiOnsiT2Zmc2V0IjoxMTcyfX0&first=100

Querying the endpoint without a cursor works just fine (https://api.twitch.tv/helix/games/top?first=100)

Are there any known issues? Although I’m aware that the Helix API is not production ready.

EDIT: All requests have been tested with and without valid OAuth tokens.

Thanks!

[BarryCarlyon]

5xx codes are “server trip up”

So just try again later!

Don’t forget to follow the rate limits! (That would be a 429 error if you exceeded there)

[geardrops]

Hi there! Helix dev here. I just double-checked your query and the service does seem to be responsive (works on my machine ). I’m sorry to hear you had this experience. I’ll be investigating if there were any issues in the service and see if any fixes need to be made. Thank you!

[HerrAusragend]

Pretty strange… I’m pulling all Twitch games to the database since the Streams API does not offer Game titles any more and I don’t have to query the API with every Stream object.

There are still some 503 error codes.

I’m using my PHP Twitch Helix Package romanzipp/Laravel-Twitch

The basic workflow of this job is also listed as Example in the README

All API requests include a valid OAuth token. The Rate Limit has been increased to 800 per min.

Cursors:

eyJiIjp7Ik9mZnNldCI6MjA0Mn0sImEiOnsiT2Zmc2V0IjoyMDU0fX0
eyJiIjp7Ik9mZnNldCI6MTk0Nn0sImEiOnsiT2Zmc2V0IjoyMDU0fX0
eyJiIjp7Ik9mZnNldCI6MTk0Nn0sImEiOnsiT2Zmc2V0IjoyMDU0fX0

[Six]

I had a similar issue a while back that was never addressed:

[Helix API] TopGames - 503 Service Unavailable

[geardrops]

Thanks for bumping this back up, folks. I’m adding it to the list of things we need to investigate. We appreciate your patience!

[Ague]

If it makes you guys feel any better, I days worth of periodic 503 errors on different endpoints. So it’s not just you. I’ve talked with @geardrops about it, so hopefully things can get resolved quickly.

[geardrops]

We’ve investigated the issue and pushed a fix out, and now you should be getting 200 and empty data instead of 503s in this case!

Thanks, everyone!

[Six]

Just did a quick test and I’m no longer getting 503s.

[Ague]

Late to the party bc of irl stuff, but I haven’t seen any 503s in my logs for a while… thx @geardrops

[geardrops]

Glad to hear it!

[HerrAusragend]

Can confirm! Awesome!