Change:
<strong>User Story:</strong> I can see whether freeCodeCamp is currently streaming on Twitch.tv. <strong>User Story:</strong> I can click the status output and be sent directly to the freeCodeCamp's Twitch.tv channel. <strong>User Story:</strong> if a Twitch user is currently streaming, I can see additional details about what they are streaming. <del> <strong>Hint:</strong> See an example call to Twitch.tv's JSONP API at <a href='http://forum.freecodecamp.org/t/use-the-twitchtv-json-api/19541' target='_blank'>http://forum.freecodecamp.org/t/use-the-twitchtv-json-api/19541</a>. <strong>Hint:</strong> The relevant documentation about this API call is here: <a href='https://dev.twitch.tv/docs/v5/reference/streams/#get-stream-by-user' target='_blank'>https://dev.twitch.tv/docs/v5/reference/streams/#get-stream-by-user</a>. </del> <ins> <strong>Hint:</strong> The relevant documentation about Twitch.tv's JSON API is here: <a href='https://dev.twitch.tv/docs/api/reference/#get-streams' target='_blank'>https://dev.twitch.tv/docs/api/reference/#get-streams</a>. </ins> <strong>Hint:</strong> Here's an array of the Twitch.tv usernames of people who regularly stream: <code>["ESL_SC2", "OgamingSC2", "cretetion", "freecodecamp", "storbeck", "habathcx", "RobotCaleb", "noobs2ninjas"]</code> <del> <strong>UPDATE:</strong> Due to a change in conditions on API usage explained <a href='https://blog.twitch.tv/client-id-required-for-kraken-api-calls-afbb8e95f843#.f8hipkht1' target='_blank'>here</a> Twitch.tv now requires an API key, but we've built a workaround. Use <a href='https://wind-bow.glitch.me' target='_blank'>https://wind-bow.glitch.me/twitch-api</a> instead of twitch's API base URL (i.e. https://api.twitch.tv/kraken ) and you'll still be able to get account information, without needing to sign up for an API key. </del> <ins> <strong>UPDATE:</strong> Due to a change in conditions on API usage, Twitch.tv requires an API key, but we've built a workaround. Use <a href='https://wind-bow.glitch.me' target='_blank'>https://wind-bow.glitch.me/helix</a> instead of twitch's API base URL (i.e. https://api.twitch.tv/helix ) and you'll still be able to get account information, without needing to sign up for an API key. </ins> Remember to use <a href='http://forum.freecodecamp.org/t/how-to-get-help-when-you-are-stuck/19514' target='_blank'>Read-Search-Ask</a> if you get stuck. When you are finished, click the "I've completed this challenge" button and include a link to your CodePen. You can get feedback on your project by sharing it with your friends on Facebook.

Discussion:
The current Twitch Tv API v5 is deprecated and will be completely replaced by the end of 2018. Just an FYI so the challenge may be updated to the new API or new challenge proposed.
thanks for bringing to this our attention! The doesn't suggest using the API directly, but instead to use a workaround we've implemented so you don't need an API key. However, this workaround may and probably does use the API V5 (someone would need to verify this). Sidenote: just for Twitch announcing the API deprecation and removal cc/
maybe a contact us page that integrates the google map API ? allows the user not only view the location but also get directions??
Just started working on the Twitch API challenge and it uses the V5 API. Also the fcc wrapper documentation says: is for V5, the new one uses . Also while at it, the wrapper should probably update the link to the documentation. It still links to , the current documentation for the V5 API is at The challenge itself already links to new location.
just to clarify, you are suggesting a new API challenge with the Google Map API? If so, that could be an interesting challenge, as it is something that many developers might want to make for themself on their own personal page. I like the idea. However, we might be able to just update the Gomix instance with the new Twitch API (I'm not sure how much effort this would take). thanks for the additional details on the Kraken vs Helix API names. Indeed, we should at least change the wrapper link.
can you open a PR with these changes?
The wrapper project is on my glitch account, and at the moment it is using my api key. I'll make camperbot's account a collaborator of the project in glitch, so freecodecamp will own the project. Is changing to the only change required ? If so I will edit my project in the next days.
The root URL of the API changing isn't the only difference. I'm still new, so someone more experienced should probably have a look at the . But I think for the and routes there should be nearly no changes necessary. The route on the other hand is completely gone in the new API. But you can get the interesting data from the route anyways.

Additionally the route now returns a instead of the name of the game, so if people should be able to display the game name in their projects we should probably implement the route to allow them to get the name from the id.
At the moment my proxy passes everything that in the url comes after to . It will not work as is with the new api. I'll update it so that if you hit the url or it use the old api, if we hit it uses the new api. What do you think ?
Sorry for the delayed answer. Yes, I'm suggesting something new :)
That appears to be a reasonable update. I haven't really looked into the new API much so we'd have to test it out. But for now, that seems like a sensible update. awesome, just checking :) If we end up not replacing it with your Google Maps API contact page, that might be a nice addition to the projects to work on.
That sounds good to me. Please let us know once you've made the change and verified that it still works!
Did you ever get a chance to update this?
No sorry. It's not so easy to make it work for both the old and new projects. Il dom 3 giu 2018, 16:37 Quincy Larson scritto:
/ / I think this issue should take high priority now since we have just a month before the API is deprecated and holiday season is starting so everyone would not be free at all times
It looks like this will be deprecated in just a couple weeks. Could you help update our Glitch project?
I'm having a look at it. I'll try to migrate to the new api before next year. In the meantime the service has a cache db and a static list of users (the ones in the example exercise). It can keep working in 'emergency' mode indefinitely serving a limited number of twitch users data. Also it seems that somebody is using it outside the scope of freeCodeCamp. I have blacklisted the domain, but we need to be careful. I'll let you know.
I have a working api locally on my computer. / do you want me to deploy it now ? or should I wait until the end of December ?

The new API will be not backward compatible, but I am serving a static data snapshot at the old enpoint , for the 8 users listed in the exercise description. The new API endpoint will be . Also, the api now is in my glitch account. I think We should transfer the ownership to freeCodeCamp (camperbot ?). Let me know.
the new api can be tested here https://em-ant-twitch- . my old twitch project still works with the served static data. I will deploy the code to wind-bow before new year. We also need to update the challenge description and update the forum post I will submit a PR with the text changes. Can anybody update the forum article ?
Yes - we should transfer ownership to CamperBot for simplicity. And I can update the forum post. What specific changes should I make?
the forum post is about CORS issues and and using jsonp callback, but the new api doesn't support anymore jsonp, and our proxy on glitch accepts cross-origin requests. We could smiply remove the link to the forum post from the challenge description, or update it with an example of the new api (with jquery, as in the old example)
which would you recommend? If you want me to update the post, I can do so - just tell me what update you'd like to make to it.
I updated the PR removing the link to the forum post. I think that post is not relevant anymore for the new api.
Awesome! Thanks for fixing this and for updating the challenge! It always feels good to close one of these issues that's nearly a year old! I've updated the old Forum post we were linking to with your updated instructions. I agree, we shouldn't link to that post anymore. But now if people end up on that post they'll have your new instructions. As always, thanks for your help, and thanks to everyone on this thread who helped us arrive at this solution!
the new version on the api is deployed on wind- it's always a pleasure to help.