Twitch · Events

Twitch User Schedule Scraper API

The Twitch User Schedule endpoint is one API call: send an account handle with your HProxy key and get back a clean, structured JSON object. Pull a Twitch streamer's upcoming schedule, with each slot's title, category, start time and whether it repeats weekly. HProxy runs the proxies, sessions, anti-bot handling and parsing server-side, so there is no headless browser to babysit and no parser to keep fixing when Twitch changes its markup. You only ever touch the JSON.
Get your API keyTwitch API reference
  • 0.15¢ per call
  • $1.49 per 1,000
  • Takes an account handle
  • Errors and timeouts are not charged

On Twitch

Profiles1Posts and media2Events1

Events

TwitchFacebook

The call

One GET, and the user schedule comes back as JSON.

Your key goes in one header. 1 required parameter, and the answer is the object below it.

The full reference
curl "https://hproxy.com/api/v1/scrape/twitch/schedule?handle=twitch" \
  -H "X-API-Key: hpx_your_key_here"
Response200 OK · JSON
{
  "segments": [
    { "title": "Ranked grind", "category": "Gaming",
      "startTime": "2026-07-30T19:00:00Z", "isRecurring": true }
  ]
}

What comes back

The Twitch user schedule object.

segments[]
Each scheduled slot with title and category.
startTime
When the slot begins, with timezone.
isRecurring
Whether the slot repeats weekly.

What it takes

Parameters.

handlestringRequiredtwitch

Account handle or @username.

trimbooleantrue

Return a slimmed-down payload (drops verbose fields).

How it works

Scraping Twitch user schedule, in three steps.

You write one line. Proxies, anti-bot walls, rendering and parsing happen on our side.

Create a free accountEvery Twitch endpoint
  1. 1

    Create a free account

    Sign up and top up any amount. The balance pays for every HProxy product.
  2. 2

    Grab your API key

    One key from the dashboard authenticates every scraper.
  3. 3

    Call the endpoint

    Send the GET you need and read the JSON. That is the entire integration.

What people build with it

Where the Twitch user schedule endpoint earns its keep.

  • Show a creator's upcoming slots inside your own product.
  • Alert a community before a stream starts.
  • Plan drops and collabs around a creator's calendar.

Twitch user schedule questions

Answered before you ask.

The reference

Send one authenticated HTTPS request to the Twitch User Schedule endpoint with an account handle and your HProxy API key. Pull a Twitch streamer's upcoming schedule, with each slot's title, category, start time and whether it repeats weekly. No proxies, no headless browser and no parsing on your side. The response is ready-to-use JSON.

This endpoint is 0.15¢ per successful call, which is $1.49 per 1,000. It bills from your HProxy balance with no subscription and no monthly minimum. Errors are retried and never charged; a lookup whose target does not exist counts as a call.

The API only accesses publicly available Twitch data, the same pages anyone can open in a browser. You are responsible for using the data in line with applicable laws and Twitch's terms for your use case.

A structured JSON object with the full user schedule data Twitch exposes publicly. See the fields listed above. The schema is consistent across calls, so you integrate once and rely on it.

No. Every call runs on HProxy's own residential network behind the scenes, so requests look like real users. The proxy layer is already included in the per-call price.

Docs and AI

Connect your scraper to an AI, any time.

The whole Scraper API is published as markdown, so an assistant reads every endpoint, every parameter and a real response without a key and writes your integration. And because a scrape is one GET that answers in JSON, an agent can run the scraper itself, on its own schedule, with your key.

Read the scraper docsSet up your assistant

Claude, ChatGPT, Cursor, Gemini, Copilot, Windsurf, Perplexity, Ollama and any assistant that speaks MCP.

The API as markdown

Paste /llms/scraper-api.txt into Claude, ChatGPT, Cursor or Copilot: every endpoint and the whole catalog, in one file. No key and no account to read it.

Open the markdown

An agent can call it

One GET with your key returns structured JSON, so an agent scrapes on its own schedule. No browser to drive, no parser to keep alive between runs.

See the endpoints

MCP server and CLI

Built by us for the free tools and hosted at mcp.hproxy.com: the proxy list, the checker and the IP lookup as tools in Claude, ChatGPT, Cursor or any assistant that speaks MCP. Nothing to install, no key.

Add it to your assistant

API docs

Every scraper endpoint documented end to end, with the parameters it takes and the response it really returns.

Read the docs

Events elsewhere

The same data on 1 other platform.

One key, one JSON shape, one balance. Move sideways without learning a second API.

Event Scraper API
Facebook Profile Events17 endpoints on Facebook

More from Twitch

4 Twitch endpoints, one key.

The Twitch catalog
Twitch ProfileProfilesTwitch User VideosPosts and mediaTwitch ClipPosts and media

Every platform

The same key works on all 23.

The whole catalog

More on the Twitch User Schedule API

What the Twitch User Schedule endpoint returns

Pull a Twitch streamer's upcoming schedule, with each slot's title, category, start time and whether it repeats weekly. The JSON object carries segments[], startTime and isRecurring. Nothing is summarised away on our side, so what you read in the response is what the Twitch user schedule page itself holds.

What you send to the Twitch User Schedule API

The call takes an account handle. Required: handle. Optional: trim. Your key travels in the X-API-Key header, the response is JSON, and the call is billed at 0.15¢, $1.49 per 1,000.

Events on other platforms

The same events data is available on 1 other platform: Facebook Profile Events. They share this endpoint's JSON shape, its per-call billing and your one API key, so moving from Twitch to another network is a change of URL rather than a second integration.

Is scraping Twitch user schedule allowed?

The endpoint reads publicly available Twitch data, the same pages anyone can open in a browser without logging in. It does not touch private accounts or anything behind a password. How you then use the data is yours to keep lawful, under the rules that apply to you and to Twitch.

Ready when you are.

Your dashboard is ten seconds away. No sales call, no subscription, no minimum.

Get startedSee every scraperTalk to us