Over the past year, we have seen streamers and their communities embrace Bits-powered experiences offered by Extensions.
As more Bits transactions are processed, we have heard feedback from developers that it is increasingly complex to maintain the benefits that are granted to viewers. Currently, developers are required to build and maintain an Extension Backend Service to validate transactions. However, if the developer’s EBS experiences an outage, it is difficult to retroactively fulfill the benefits to viewers who have already spent Bits. To ease this pain point, we are happy to announce a new Bits Transaction API. The API will let developers retrieve timestamped transaction history for each of their Extensions across all of Twitch. This will allow developers to “replay” the missing transactions and fulfill the relevant benefits to viewers.
What’s in the box
The API consists of a single endpoint
GET https://api.twitch.tv/helix/extensions/transactions, which requires an app access token. (Refer to our Authentication documentation for more information on how to generate a token). The endpoint allows developers to retrieve historical Bits transactions that have occurred via their Extension across all channels where the Extension was activated.
There is a corresponding Webhooks functionality that allows developers to be notified of new Bits transactions.
To get started