The API recently started returning only Internal Server Error when updating the channel’s game and/or title through version 3 of the API.
CURL:
curl -X PUT -d arg=val -d "channel%5Bstatus%5D=test" -H "Accept:application/vnd.twitchtv.v3+json" -H "Authorization:OAuth {INSERT TOKEN}" https://api.twitch.tv/kraken/channels/moocat
Response:
{"error":"Internal Server Error","status":500,"message":""}
The change itself goes through, but the response returns the error and 500 HTTP status code.
Hello, according to blog posts v3 was removed in February of this year. Move over to V5 (Kraken) or if you’re alright with limited endpoints, to alleviate the need to refactor in November, use Helix!
You need to migrate your code to use v5. On February 14, 2017, we will be removing v1 and v2 of the API and transition v3 into a deprecated state. In one year (February 14, 2018), v3 will be removed from the API. We hope that this gives enough transition time for your integrations. - Source: https://blog.twitch.tv/action-required-twitch-api-version-update-f3a21e6c3410
Kraken Docs:
Helix Docs:
Release Notes:
Be sure to research before committing to Helix, though, there are many endpoints still missing, but bare in mind that Kraken will no longer be in service as of December.
That’s outdated info, v3 wasn’t removed, it was planned to be removed but one thing lead to another and Helix became a thing, and along with the announcement of v5 deprecation/removal the removal of v3 endpoints was pushed back to be in line with that of v5. The docs page shows the important dates Twitch API | Twitch Developers
with the key thing being Note: The default version of the API is v3 until Dec. 31, 2018. However, both v3 and v5 are deprecated and will be removed altogether at the end of 2018.
As for the original issue, this is the 2nd time I’ve seen someone recently have 500 errors on the v3 version of that endpoint. I’m not sure what the issue is as I don’t use v3 myself any more, well, except from a few undocumented endpoints 
I stand corrected, I had actually referenced that “chart” as well, but read the deprecation date as the removed date by mistake. Oops.
Would love to know if this is being looked in to, or if I should find a different way of setting the game/title.
Someone raised the same issue on the DevServer. So it’s not just you with this one.
The change goes thru, but gets a 500 Err.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.