New API (rate limiting) for large service & webhooks

Hello everyone !

The revelations of the last few days concerning development on Twitch were very “exciting”,
We wait on our side with impatience to be able to create and develop with all this!

However, we have some concerns and questions about one thing.

The new limitations that should happen on the new API is one of those things, and that worries us a little bit.

Let me explain:

Over the last few years, we have been developing more and more features that make the best use of the Twitch API to provide the most up-to-date content possible.
The number of queries to the API is substantial by default, and even more with the number of our users that grew from day to day.
For our performance and in order to respectfully use the resources we are given, we have and do optimizations to divide the number of calls to the APIs.

The arrival of the webhooks will allow to withdraw 70% of these calls.

But the rest of the calls will still be important, even if we optimize our systems as much as possible.
The number of our users being the main cause (As an example, we plan to reach 270,000 users by the end of the year).

Our concern is therefore, whether the deployment of this limitation will take into account this type of problem ?


Even though the revelation is still very recent, we have some questions about webhooks.

Is it planned to deploy several additional webhooks that originally planned?
Namely, the change information of the channel (Statut, game, profil banner, etc.)?

Thank you in advance :slight_smile:

Regards,
Dere011.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.