Não vamos ter esta publicação no seu idioma. Confira outras opções aqui:
Today, we are announcing the deprecation and sunset plan for WebSub webhooks – our non-EventSub webhooks product.
When EventSub was announced during Developer Day 2020, we discussed the benefits of an event-based and transport-agnostic product and how this approach would be the future for retrieving real-time events from Twitch. We also mentioned that when EventSub had subscription types that matched the functionality of WebSub, we would deprecate WebSub. Since the launch, we’ve added 14 more subscription types to EventSub, getting us to parity with what is offered via WebSub and adding support for features like Raids, Polls, and Predictions.
Now that EventSub has subscription types that match the topics in WebSub, WebSub is now deprecated. Starting today, Twitch application client IDs that have not previously accessed WebSub can no longer access WebSub. Client IDs that currently use WebSub can continue to use WebSub until it is decommissioned on or soon after September 16, 2021.
For developers who have not migrated from WebSub to EventSub just yet, you have improvements to look forward to. EventSub fixes some of the challenges you may have experienced with past webhooks, such as no longer requiring resubscribing to topics and retrieving more robust information in payloads. In addition, EventSub’s subscription limit scales with the number of users who have authorized your application, so it’s easier to scale as your application grows. We also provide the Twitch CLI to make a migration easier, allowing you to mock events and see the payload difference between equivalent topics.
We are thrilled with the support we’ve received from the developer community for the EventSub product and we’re working hard to add more subscription types and transports to EventSub soon. Some of our best ideas have come from the UserVoice ideas you’ve shared with us. Thank you. We’re excited to keep hearing from you and improving EventSub. To get started with EventSub, please visit the EventSub documentation.