Closed strager closed 1 year ago
In order to support revocations (#13), we need to keep track of redemption IDs sent by Twitch. I also want the redemption ID in case we receive duplicate redemption messages (e.g. if we create multiple WebSocket connections for redundancy).
The redemption ID is just the ["event"]["id"] string in the EventSub notification payload. Exampled ID: "addae886-719e-4427-8f19-8152a260a806" (It's different from the reward ID.) https://dev.twitch.tv/docs/eventsub/eventsub-subscription-types/#channelchannel_points_custom_reward_redemptionadd
["event"]["id"]
"addae886-719e-4427-8f19-8152a260a806"
Implemented in 78277f7dcec26ca272a87b7fff83ba0e1b47e5fb.
In order to support revocations (#13), we need to keep track of redemption IDs sent by Twitch. I also want the redemption ID in case we receive duplicate redemption messages (e.g. if we create multiple WebSocket connections for redundancy).
The redemption ID is just the
["event"]["id"]
string in the EventSub notification payload. Exampled ID:"addae886-719e-4427-8f19-8152a260a806"
(It's different from the reward ID.) https://dev.twitch.tv/docs/eventsub/eventsub-subscription-types/#channelchannel_points_custom_reward_redemptionadd