-
Notifications
You must be signed in to change notification settings - Fork 379
API
The Twitch API allows websites to develop your own applications based on the rich feature set that we provide. This includes getting information about what streams are live, changing information about specific channels, or doing a SSO integration with Twitch itself. This documents lists the resources that the Twitch API provides. If you have any questions or need any help in using this API, please visit the API Developers Group or Github Issues
The Twitch API is comprised of two parts: the REST API itself and the JavaScript SDK that allows for easy integration into any website. Most users will only need to use the JS SDK, but if you want a deeper integration (for example, for use with Python or PHP scripts) you may access the REST API directly. The RESTful Integration Guide should help you if that describes your needs.
The base URL for all API resources is https://api.twitch.tv/kraken.
All data is sent and received as JSON.
Blank fields are included as null instead of being omitted.
All API methods support JSON-P by providing a callback parameter with the request.
curl https://api.twitch.tv/kraken?callback=foo
All error responses are in the following format, delivered with the corresponding status code:
{
"message":"Invalid Token",
"status":401,
"error":"Unauthorized"
}
When using JSON-P, the status code will always be 200 to allow browsers to parse it. Check the body of the response for the actual error data.
The returned MIME type from requests follows the format:
application/vnd.twitchtv[.version].param[+json]
Clients may specify the following MIME types:
application/json
application/vnd.twitchtv+json
application/vnd.twitchtv[.version]+json
This allows clients to get either the latest version of the API or a specific version.
OAuth 2 is an authentication protocol designed to make accessing user accounts from third party clients easy and secure. An access_token given to your application allows you to perform actions on behalf of an authenticated Twitch user.
There are two ways to get access tokens, a browser-based flow for use on most applications, and a password credentials flow, which works best on embedded applications which aren't able to integrate a browser (hardware streaming products, game consoles). The rest of this section covers the browser-based flow.
Before you can handle user authorization in your app, register a client application. The specified redirect_uri will receive the result of all client authorizations in JSON: either an access token or a failure message.
Next, direct users on your application to the authorization endpoint, where they will log in or register on Twitch and approve access for your application. You can include the following URL parameters:
-
response_type(required):token. -
client_id(required): The Client ID of your app that you recieved upon creation. -
redirect_uri(required): The URL that clients will be forwarded to upon approval. -
scope(required): A space separated list of scopes your app is requesting approval for to be displayed to the user. -
state(recommended): A string that maintains state between the request and callback toredirect_uri. This can be useful for allowing your application to associate an authorization with a specific user request.
An example authorization request:
https://api.twitch.tv/kraken/oauth2/authorize?redirect_uri=http://example.com&client_id=i29g16w8403x4s196d47tavi&response_type=token&scope=user_read+channel_read&state=user_dayjay
Once your application is authorized, the user will be forwarded to the specified request_uri with a URL fragment containing access_token and scope parameters. URL fragments can be accessed from JavaScript with document.location.hash.
http://example.com/#access_token=bb09tmrqbxbgvlny25pbm5kfs&scope=user_read+channel_read
That's it! Your application can now make requests on behalf of the user by including your access token as specified in Authentication.
When requesting authorization from users, the scope parameter allows you to specify which permissions your app requires. Without specifying scopes, your app only has access to basic information about the authenticated user. You may specify any or all of the following scopes:
-
user_read: Read access to non-public user information, such as email address. -
channel_read: Read access to non-public channel information, including email address and stream key. -
channel_editor: Write access to channel metadata (game, status, other metadata). -
channel_commercial: Access to trigger commercials on channel. -
channel_stream: Ability to reset a channel's stream key.
Scopes are specified as a space separated list in the url parameter scope when requesting authorization:
&scope=user_read+channel_read
Your app should ask for the minimum permissions that allow you to perform needed actions.
We do not allow username/password authentication. All clients must use OAuth 2.
Send token as header:
curl -H "Authorization: OAuth OAUTH-TOKEN" https://api.twitch.tv/kraken
Send token as URL parameter:
curl https://api.twitch.tv/kraken?oauth_token=OAUTH-TOKEN
/
Basic information about the API and authentication status. If you are authenticated, the response includes the status of your token and links to other related resources.
{
"token": {
"authorization": {
"scopes": ["user_read", "channel_read", "channel_commercial", "user_read"],
"created_at": "2012-05-08T21:55:12Z",
"updated_at": "2012-05-17T21:32:13Z"
},
"valid": true
},
"_links": {
"channel": "https://api.twitch.tv/kraken/channel",
"users": "https://api.twitch.tv/kraken/users/hebo",
"user": "https://api.twitch.tv/kraken/user",
"channels": "https://api.twitch.tv/kraken/channels/hebo",
"chat": "https://api.twitch.tv/kraken/chat/hebo"
}
}