twitch Getting started with twitch Requesting a token

Example

The Implicit Grant flow is best suited for Web applications. It's easily integrated into a website using JavaScript and doesn't require a server to store the authorization code to retrieve a token.

You'll first send the user to the Twitch authorization endpoint. This URL is made up of a the base authorization URL (https://api.twitch.tv/kraken/oauth2/authorize) and query string parameters that define what you're requesting. The required parameters are response_type, client_id, redirect_uri, and scope.

For the Implicit Grant flow, the response_type parameter is always set to token. This signifies that you're requesting an OAuth token directly.

The redirect_uri is where the user will be redirected after they approve the scopes your application requested. This must match what you registered on your Twitch account Connections page.

The client_id is a unique identifier for your application. You can find your client ID on the Connections page, too.

The scope parameter defines what you have access to on behalf of the user. You should only request the minimum that you need for your application to function. You can find the list of scopes on the Twitch API GitHub.

The state parameter is also supported to help protect against cross-site scripting attacks. When the user is redirected after authorization, this value will be included on the redirect_uri.

Redirect the user to this URL:

https://api.twitch.tv/kraken/oauth2/authorize
    ?response_type=token
    &client_id=[your client ID]
    &redirect_uri=[your registered redirect URI]
    &scope=[space separated list of scopes]
    &state=[your provided unique token]