OAuth 2.1
The Kick OAuth Flow.
Token Types
There are 2 types of tokens that are available for the Kick Dev API: App Access Token and User Access Token. Each token has a unique OAuth flow to generate the token and are generally used in different scenarios.
App Access Token
App Access Tokens are generated through the Client Credentials flow. These server-to-server API tokens are the most basic form of token for accessing the API. They can access publicly available data and are ideal for use when user login is not required.
User Access Token
User Access Tokens are generated through the Authorization Grant flow. These tokens give an application access to the user’s information based on the scopes the App has requested. This gives more privileged information and access to an App and will often allow an App to act on the user’s behalf.
Kick OAuth Server
The Kick OAuth server is hosted on id.kick.com.
Information from creating an App will be required in these endpoints. Checkout the Kick Apps Setup page to get the information for your App.
The host URL for our OAuth server is different from our API server.
The host URL is: https://id.kick.com
Authorization Endpoint
Authorization
Directs the user to the authorization server where they can log in and approve the application’s access request.
Query Parameters
Your application’s client ID
Must be code
The URI to redirect users to after authorization
A random string to maintain state between the request and callback
Space-separated list of scopes for request
OAuth code challenge
Must be S256
Response
Example
Token Endpoint
Token
Exchanges the code for a valid access token and a refresh token that can be used to make authorised requests to Kick’s API.
Headers
Must be application/x-www-form-urlencoded
Request Body
Code received during the Authorization Flow
Your application’s client ID
Your application’s client secret
The URI to redirect users to after authorization
Must be authorization_code
To verify PKCE challenge code created
Response
Example
App Access Token Endpoint
App Access Token
Uses a client_id and client_secret to generate an app access token which can be used to obtain public data on Kick.
Headers
Must be application/x-www-form-urlencoded
Request Body
Your application’s client ID
Your application’s client secret
Must be client_credentials
Response
Example
Refresh Token Endpoint
Refresh Token
Pass in refresh token and refresh both access and refresh codes.
Headers
Must be application/x-www-form-urlencoded
Request Body
Code received during the Authorization Flow
Your application’s client ID
Your application’s client secret
Must be refresh_token
Response
Example
Revoke Token Endpoint
Revoke Token
Pass in a token to revoke access to that token.
Headers
Must be application/x-www-form-urlencoded
Query Parameters
The token to be revoked
access_token
or refresh_token
Response
OK
OK