I work for an agency that works with streamers and we currently have a flow on make.com where when a user subscribes to the streamer we get the sub’s data (user login, user name, is_gift, and sub time), but we’re currently shifting from an out-of-the box solution to creating our own application using AWS API Gateway and Lambda to receive EventSub’s notifications.
The problem is we’re getting a “subscription missing proper authorization” message when trying to subscribe to “channel.subscribe”. I understand we need the authorisation from the user via the “channel:read:subscriptions” scope, and I understand that we should do that using an oAuth flow. What I can’t wrap my head around is the fact that I don’t intend to create an application outside of twitch to receive the notification.
What I aim for is: when a user subscribes to our streamers, we get the sub’s data in our servers, just like we use from make.com. The flow should be: when a user subscribes to streamer ‘X’, we receive a notification with data regarding this subscription. I don’t understand where the “https://id.twitch.tv/oauth2/authorize?[parameters]” should come into play since I’m not creating an application that allows users to subscribe to a streamer, I just want the sub’s data! It’s as simple as that and I can’t understand how to achieve my goal from reading the documentation.