Guides · social · Popular APIs
Register an application in the Twitch Developer Console (2FA required) to get a client ID and client secret for OAuth and the Twitch API.
Researched · not yet run liveLast researched 25 October 2026 · Twitch · provider site
A Twitch user account (with verified email and 2FA) owns applications registered in the Developer Console.
Organisation ownership of apps (Twitch Developer organisations) is not covered in the pages reviewed. [to verify]
Steps marked “human step” are ones only you can do: verapli never signs in, submits, pays or accepts terms for you.
Log in at dev.twitch.tv/console with your Twitch account. If you have no account you create it yourself; verapli does not create accounts. Verify your email first.
Where: https://dev.twitch.tv/console
In Twitch Security and Privacy settings, turn on two-factor authentication, then refresh the console.
Where: https://www.twitch.tv/settings/security
Read the Twitch Developer Services Agreement, which governs use of Twitch APIs and Twitch Data, before registering an application.
Where: https://legal.twitch.com/en/legal/developer-agreement/
In Applications, click Register Your Application. Enter a name unique across all Twitch applications, add your OAuth Redirect URLs (click Add for each), pick a Category, complete the CAPTCHA and click Create. Then open Manage and copy the Client ID.
verapli captures TWITCH_CLIENT_ID here by plain code: encrypted in your browser, never shown to AI.
Where: https://dev.twitch.tv/console/apps
On the app's Manage page, click New Secret and copy it straight away; verapli writes it to your env file. Generating a new secret invalidates the previous one.
verapli captures TWITCH_CLIENT_SECRET here by plain code: encrypted in your browser, never shown to AI.
Where: https://dev.twitch.tv/console/apps
Plain-English summary, not legal advice. Each card links its source.
Twitch Data, including data you collect about Twitch end users and insights derived from it, may not be sold, licensed, monetised, distributed for commercial purposes or shared with affiliates or third parties without Twitch's prior written permission. Transferring end user data to ad networks or data brokers is prohibited. [to verify] exact section numbers against the live agreement. [3]
Twitch will consider authorising certain activities, including marketing services, only under a separate agreement and approval process. Using end users' channel content to promote a commercial product needs those users' authorisation. [to verify] [3]
Earning from Bits in Extensions requires the separate Twitch Extensions Developer Agreement; Bits revenue is shared between the broadcaster and the developer. [4]
The API uses a per-minute token bucket (default 1 point per request) with separate buckets for app and user tokens; user-token limits are per client ID per user. Exhausting the bucket returns 429; use Ratelimit-Reset to back off. The documented example shows Ratelimit-Limit 800. [2]
| Env var | Secret | Format | What it is |
|---|---|---|---|
TWITCH_CLIENT_ID | not secret | lowercase alphanumeric string, e.g. abc123… [to verify] | Twitch application client ID (public; sent as the Client-Id header) |
TWITCH_CLIENT_SECRET | secret | lowercase alphanumeric string… [to verify] | Twitch application client secret, used for app access tokens and the authorization code flow |
Source [1]
The same entry as JSON: /api/v1/entries/twitch/developer · requirements /api/v1/requirements/twitch/developer · terms /api/v1/terms/twitch/developer.
claude mcp add --transport http verapli https://verapli.com/mcp
> "What do I need for Twitch Developer application (Helix API), and how long will it take?"
→ tools/call requirements { "provider_id": "twitch/developer" }Provider rules change. This page is generated from verapli registry version 2026.1025.387; spotted something out of date? Tell us. Twitch is not affiliated with verapli.