Step 1 - Redirect to Twitch
Step 2 - user accepts (or delcines) the account/clientID Link
Step 3 - under regular/code auth they come back to your redirecURL with a ?code
Step 4 - exchange the code for a token.
But if you are doing this in a pure JS environment then you use implict auth
Okay, I don’t know if I have to make an other post for my question but I’m wondering if pick the right flow for the access token.
I choose to get a Authorization code grant flow, but maybe I had to get this one with Implicit grant flow ?
Thank you very much, I think the twitch CLI will be a good start.
But I’m afraid for the futur, because I know that for the follower list, I will have to make some ajax call to twitch, and maybe those call wil get the same problems with CORS.
And for what you said, my application is hosted on a local server which is Laragon (similar to WAMP/XAMP), and it work with the PHP Framework Laravel, so for that I think I’m good.
So in a local server, will it work with the CORS ? In my memories, I have made a previous application with the same configuration (Laragon with Laravel) which was connected to Twitch, and I had no problem with the CORS. Maybe the security has been updated since this time.