Twitch Tv Twitch Helix API
Official vendor OpenAPI document · agent-readyMediaImage ProcessingapiKey, bearer, oauth2137 EndpointsREST
For Agents
Programmatically start commercial, get ad schedule. Covers 137 operations with apiKey, bearer, oauth2 authentication.
Use for: I need to start commercial, I want to ad schedule, Search for snooze next ad, Find all extension analytics
Not supported: Does not handle payments, communications, or crm - use for media and content only.
The Twitch Helix API is a RESTful API that lets developers build creative integrations for the broader Twitch community. The API exposes 137 endpoints secured with apiKey, bearer, oauth2 authentication.
Install Jentic One Beta
Connect the Twitch Helix API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Twitch Helix API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ftwitch.tv%2Ftwitch" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ftwitch.tv%2Ftwitch" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Twitch Helix API.
Start Commercial
Get Ad Schedule
Snooze Next Ad
Query and filter Twitch Helix API records by parameters
Monitor Twitch Helix API operational status and events
Use Cases
Patterns agents use Twitch Helix API for, with concrete tasks.
★ Media and Content Operations
Use the Twitch Helix API to perform media operations programmatically. The API provides 137 endpoints covering core functionality including start commercial, get ad schedule, snooze next ad.
Call POST /channels/commercial to start commercial
Automated Analytics Management
Automate analytics operations by combining multiple Twitch Helix API endpoints. Agents can get ad schedule and then snooze next ad in a single workflow.
Call GET /channels/ads to get ad schedule, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Twitch Helix API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey, bearer, oauth2 tokens manually.
Search Jentic for 'start commercial', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
137 endpoints — the twitch helix api is a restful api that lets developers build creative integrations for the broader twitch community.
METHOD
PATH
DESCRIPTION
POST
/channels/commercial
Start Commercial
GET
/channels/ads
Get Ad Schedule
POST
/channels/ads/schedule/snooze
Snooze Next Ad
GET
/analytics/extensions
Get Extension Analytics
GET
/analytics/games
Get Game Analytics
GET
/bits/leaderboard
Get Bits Leaderboard
GET
/bits/cheermotes
Get Cheermotes
GET
/extensions/transactions
Get Extension Transactions
POST
/channels/commercial
Start Commercial
GET
/channels/ads
Get Ad Schedule
POST
/channels/ads/schedule/snooze
Snooze Next Ad
GET
/analytics/extensions
Get Extension Analytics
GET
/analytics/games
Get Game Analytics
GET
/bits/leaderboard
Get Bits Leaderboard
GET
/bits/cheermotes
Get Cheermotes
GET
/extensions/transactions
Get Extension Transactions
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Twitch Helix API by hand means sending both a Client-Id header and a bearer or OAuth 2.0 user token on every call, matching each operation to the scopes it requires, and handling pagination and rate limits yourself. Through Jentic you install once, import the Twitch Helix API from the API Directory, store the Client-Id and token once, and your agent calls it.
Permission scoping
Twitch Helix routes its write and analytics targets through the request body and query parameters rather than the URL path, so scope your agent to the operations it needs, such as reading the bits leaderboard or extension analytics. You choose the operations it may call, so a write like starting a commercial or snoozing ad scheduling is not included unless you add it.
Credential isolation
Your Twitch Client-Id and token are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'read the bits leaderboard' or 'get extension analytics', and Jentic returns the matching Twitch Helix operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Twitch Helix API through Jentic.
What authentication does the Twitch Helix API use?
The Twitch Helix API uses apiKey, bearer, oauth2 authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.
Can I start commercial with the Twitch Helix API?
Yes. Use the POST /channels/commercial endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Twitch Helix API?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I start commercial through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'start commercial'. Jentic returns the matching Twitch Helix API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Twitch Helix API have?
The Twitch Helix API exposes 137 endpoints covering analytics, bits, channel_points operations.
Can I limit what my agent is allowed to do with the Twitch Helix API?
Yes. Jentic One is self-hosted, so your own rules decide which Twitch Helix operations and credentials the agent may use. Because Twitch routes its write and analytics targets through the request body and query parameters rather than the URL path, you scope the agent to just the operations it needs, such as reading the bits leaderboard or getting extension analytics. A write like starting a commercial or snoozing ad scheduling is not included unless you explicitly add it, and the stored Client-Id and token are injected only for the calls you have allowed.
GET STARTED