Well the other thing you need to access the Twitch API is a logged in user to provide an access token, or using a ClientID/Secret to generate an access token.
According to the other post I mentioned, the one endpoint I actually need only needs a client ID, unless that info is out of date?
A “wrapper” doesn’t take a clientID, the user using the wrapper supplies a clientID to work with right?
So you don’t need a clientID, the user using your wrapper does.
that’s true
Sure for testing you’ll need to use a clientID but only you’ll be using that as users of your library will provide their own credentials. You won’t distribute the library containing your clientID.
I see. Thanks for the info!