My name is Chris and I run the engineering team responsible for the third-party API platform at Twitch in partnership with my colleague Travis, Director of Developer Relations.
First off, we made a mistake. We haven’t done a good enough job explaining what we’re trying to do and how we’re going to go about doing it. Travis and I take responsibility for that, apologize, and want you to know we’re committed to doing better.
So what are we going to do about it?
We will delay the implementation of v5 rate limiting until further notice. It’s not reasonable to ask people to migrate off of an old thing before the new thing is ready! There is good news on that front though.
The engineering work required to migrate all of the legacy functionality we have committed to supporting in the new Twitch API has been completed. So we’re close to being able to provide the community with a migration path off of v5. In the next few weeks, we’ll be gathering feedback from members of the community on this functionality and then making it generally available once we’re confident all the bugs have been worked out.
We’re making these changes in order to be better partners to all of you. Managing disparate systems can be burdensome and lead to errors, so we’re encouraging developers to migrate to our new system. Imposing measures such as rate limits is designed to curb and prevent abuse. We want to continue to serve the community, yet some bad actors can spoil it for others. We hope this helps illustrate the balance we are intending to strike with our plans, and demonstrates our continued commitment to Twitch Developers.
Stability is important, but Twitch is constantly growing and evolving. A completely immutable system isn’t compatible with that. For instance, we recently announced v5 changes to the streams endpoints due to a migration to a new backend system that deals with live channels. The previous system was at its scaling limit and we had to build something new. To make the new system scale, we had to make some tradeoffs in functionality. These things will continue to happen as we grow, but it’s our responsibility to communicate those to you clearly and transparently.
Twitch and the developer community are partners. We’ve heard your feedback and are working on it. A vibrant third-party developer community is important to Twitch and we’re committed to working together with you in the future.
Director of Engineering - API & Browser
Director of Developer Relations