Nexscope

Twitch User Schedule

Read a Twitch user's schedule by handle, including event start and end times, titles, descriptions and thumbnails. Paginate using the returned cursor.

CostAt least 10 credits / call
Try online
POST · https://api.nexscope.ai/social/twitch/user/scheduleMCP · social_twitch_user_schedule

What this API does

Read a Twitch user's schedule by handle, including event start and end times, titles, descriptions and thumbnails. Paginate using the returned cursor. The request accepts handle. Its documented result includes platform, resourceStatus.

Twitch User Schedule API use cases

Plan a Twitch User Schedule request

A researcher checks the published operation description and supplies handle for Twitch User Schedule. The request stays within the supported parameters rather than assuming other platform capabilities.

Inspect Twitch User Schedule results

An analyst reviews platform, resourceStatus from Twitch User Schedule for the requested subject. Missing values remain explicit, and the response does not establish complete platform coverage.

Document Twitch User Schedule observations

A researcher records the inputs and available results from Twitch User Schedule alongside its published description. The record supports a scoped review without inferring unsupported actions, refresh intervals or broader conclusions.

Twitch User Schedule API FAQ

What does the Twitch User Schedule API return?

Read a Twitch user's schedule by handle, including event start and end times, titles, descriptions and thumbnails. Paginate using the returned cursor. The documented output includes platform, resourceStatus. It corresponds to the supplied handle. Optional fields can be absent; a missing value should not be interpreted as a measured zero. Example values illustrate the response shape, rather than live account results.

How many credits does the Twitch User Schedule API cost?

The current documented cost is At least 10 credits / call. This is the same cost shown at the top of this page. If a range or estimate is displayed, the final charge depends on the request. Review your available credits and the pricing page before calling the API, and check API usage records for the actual charge.

How do I call the Twitch User Schedule API from my app or an MCP client?

Send a POST request to https://api.nexscope.ai/social/twitch/user/schedule with your API key as a Bearer token and the JSON inputs shown in API integration. In a compatible MCP client such as Claude or Cursor, connect Nexscope and call social_twitch_user_schedule. Use the MCP arguments shown in the MCP guide, or switch Online test to MCP to review its request before adding it to your app.

View plans and creditsConnect this API with MCP

Try this API
Endpoint
https://api.nexscope.ai/social/twitch/user/schedule
MCP method
social_twitch_user_schedule

Step 1 of 3 · Authenticate

Authentication

All run endpoints require a user API key. Send it as a bearer token in the Authorization header.

Authorization: Bearer nk-xxxxxxxxxxxxxxxxx
Missing or invalid API keys return an authentication error. Manage keys from .

Step 2 of 3 · Send a request

POSThttps://api.nexscope.ai/social/twitch/user/schedule

Run an API

Send a JSON request body using the parameters described below.

Example request

Replace YOUR_API_KEY, then run this command in your terminal.

curl -X POST 'https://api.nexscope.ai/social/twitch/user/schedule' \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "handle": "emongg"
}'

Code example

{
  "handle": "emongg"
}

Step 3 of 3 · Inspect the result

Check the response

Read code for the request status and data for the result. Open the parameter and response reference for the full field definitions.

HTTP status codes

CodeDescription
200Default HTTP response for both success and many business errors. Only outer JSON code 0 indicates success or asynchronous acceptance; inspect data for the result.
429Execution admission rate limit; honor Retry-After when present.
503Execution admission is temporarily unavailable; honor Retry-After when present.
Opt-inX-Nexscope-Http-Status: semantic maps controller-handled business errors to HTTP status on run and task routes. Pre-authentication failures, such as a missing API key (code 11209), may still return HTTP 200 before this mapping. Always check the outer JSON code; malformed requests and infrastructure failures may also return non-200 HTTP responses.
All categories/ Social Data
POSThttps://api.nexscope.ai/social/twitch/user/schedule

Run this API

Send a JSON request to execute this API and receive the documented response payload.

Endpoint

MethodPOST
Pathhttps://api.nexscope.ai/social/twitch/user/schedule
AuthBearer API key
Content-Typeapplication/json

Request parameters

NameTypeRequiredDescription
handlestringrequired
Twitch handle
Example: emongg

Social data contract

Use your Nexscope API key. No supplier credentials are required. Requests reject unknown fields, including pageSize. URLs require HTTPS and an exact supported platform host and resource path. Documented YouTube video URLs may use youtu.be; other short links are unsupported. Check the request schema for supported fields and defaults.

Each request fetches one page. Continue manually with the returned nextCursor, or nextPage for Instagram Reels (pages 1–11). Cursors are opaque, unchanged strings up to 65536 UTF-8 bytes. No automatic pagination, retry, media download or transcription is performed. Repeated requests may purchase data again.

Resource status is independent of HTTP and billing: AVAILABLE, PARTIAL, PRIVATE, RESTRICTED, NOT_FOUND, NO_TRANSCRIPT or UNKNOWN can accompany code 0. Unknown values remain null; arrays remain empty arrays. fetchedAt is the response observation time; sourceFetchedAt is null without source evidence.

usage.billingStatus is NOT_CHARGED, SETTLED or UNKNOWN; chargedCredits is null when unconfirmed. Unknown charges never mean free. Completed lookups have a minimum charge of 10 credits, including cached, no-caption and unavailable-resource results; check API usage records for the actual charge. Parameter errors and unpublished APIs use the standard error envelope; upstream failures use code 13007, rate limits 429 and timeouts 408. Always check code and msg.

Response example

Platform response envelope. code 0 indicates success or acceptance; data contains the business result.

{
  "code": 0,
  "cost": "-1",
  "data": {
    "data": {
      "__typename": "User",
      "broadcastSettings": {
        "__typename": "BroadcastSettings",
        "id": "23220337",
        "title": "Checking out Diablo IV: Lord of Hatred! !diablo #DiabloPartner #ad"
      },
      "channel": {
        "__typename": "Channel",
        "id": "23220337",
        "schedule": {
          "__typename": "Schedule",
          "id": "schedule-23220337",
          "interruption": null,
          "nextSegment": {
            "__typename": "ScheduleSegment",
            "id": "eyJzZWdtZW50SUQiOiI4ZThhMTczMS1hYjU0LTQxZDMtOTEzMy02N2JjZTM0NTRiMzUiLCJpc29ZZWFyIjoyMDI2LCJpc29XZWVrIjoxOH0=",
            "startAt": "2026-05-03T11:00:00Z"
          },
          "segments": [
            {
              "__typename": "ScheduleSegment",
              "baseSegmentID": "96555c00-78fd-4854-a22e-dacc8e7efec9",
              "cancelledUntil": null,
              "categories": [],
              "endAt": "2026-04-27T21:00:00Z",
              "hasReminder": false,
              "id": "eyJzZWdtZW50SUQiOiI5NjU1NWMwMC03OGZkLTQ4NTQtYTIyZS1kYWNjOGU3ZWZlYzkiLCJpc29ZZWFyIjoyMDI2LCJpc29XZWVrIjoxOH0=",
              "isCancelled": false,
              "repeatEndsAfterCount": null,
              "startAt": "2026-04-27T11:00:00Z",
              "title": ""
            }
          ]
        }
      },
      "id": "23220337",
      "lastBroadcast": {
        "__typename": "Broadcast",
        "id": "318502443360",
        "startedAt": "2026-05-02T08:26:08.899139Z"
      },
      "primaryColorHex": null,
      "stream": {
        "__typename": "Stream",
        "createdAt": "2026-05-02T08:26:00Z",
        "game": {
          "__typename": "Game",
          "id": "515024",
          "name": "Diablo IV",
          "slug": "diablo-iv"
        },
        "height": 900,
        "id": "318502443360",
        "isDualFormat": false,
        "previewImageURL": "https://static-cdn.jtvnw.net/previews-ttv/live_user_emongg-320x180.jpg",
        "verticalPreviewImageURL": "https://static-cdn.jtvnw.net/previews-ttv/live_user_emongg-180x320.jpg",
        "viewersCount": 2994,
        "width": 1600
      },
      "success": true,
      "videos": {
        "__typename": "VideoConnection",
        "edges": [
          {
            "__typename": "VideoEdge",
            "node": {
              "__typename": "Video",
              "createdAt": "2026-05-02T08:26:09Z",
              "game": {
                "__typename": "Game",
                "id": "515025",
                "name": "Overwatch",
                "slug": "overwatch-2"
              },
              "id": "2762226372",
              "lengthSeconds": 41352,
              "previewThumbnailURL": "https://vod-secure.twitch.tv/_404/404_processing_320x180.png",
              "title": "[!DROPS ENABLED + WINTON BADGE] watching owcs, gaming",
              "viewCount": 196
            }
          }
        ]
      }
    },
    "platform": "twitch",
    "resourceStatus": "AVAILABLE",
    "usage": {
      "billingStatus": "UNKNOWN"
    }
  },
  "msg": null,
  "time": "2026-01-01 00:00:00",
  "traceId": null,
  "ts": "0"
}

Response fields

NameTypeRequiredDescription
codeintegerrequired
0 means accepted or successful; nonzero is a platform error.
coststringrequired
Elapsed milliseconds, never credits; -1 outside web requests.
dataanyrequired
Data value used by this API operation.
msgstring | nullrequired
Msg value used by this API operation.
timestringrequired
Server local time: yyyy-MM-dd HH:mm:ss.
traceIdstring | nullrequired
Trace id value used by this API operation.
tsstringrequired
Epoch milliseconds.

Any of option 1 — requires platform, resourceStatus, data, usage

NameTypeRequiredDescription
dataobjectrequired
Data value used by this API operation.
data.dataobjectrequired
Data value used by this API operation.
data.platformstringrequired
Platform value used by this API operation.
data.resourceStatusstringrequired
Resource status value used by this API operation.
data.usageobjectrequired
Usage value used by this API operation.

Any of option 2

NameTypeRequiredDescription
datanullrequired
Data value used by this API operation.

Responses

CodeDescription
200Default HTTP response for both success and many business errors. Only outer JSON code 0 indicates success or asynchronous acceptance; inspect data for the result.
429Execution admission rate limit; honor Retry-After when present.
503Execution admission is temporarily unavailable; honor Retry-After when present.
Opt-inX-Nexscope-Http-Status: semantic maps controller-handled business errors to HTTP status on run and task routes. Pre-authentication failures, such as a missing API key (code 11209), may still return HTTP 200 before this mapping. Always check the outer JSON code; malformed requests and infrastructure failures may also return non-200 HTTP responses.

Data source, freshness, and limitations

Source, freshness, coverage, rate limits, and estimation notes are not specified in this API definition unless they appear in the request or response field documentation above. Do not assume official marketplace data or real-time freshness when it is not explicitly documented.

Step 1 of 2 · Connect your MCP client

MCP

V2 recommended

Connect remote agents through the standard MCP 2025-11-25 Streamable HTTP endpoint. Use OAuth 2.1 Authorization Code with PKCE, or an API key for compatibility.

POST https://api.nexscope.ai/mcp
MCP-Protocol-Version: 2025-11-25
Content-Type: application/json
Authentication

OAuth clients request the mcp:tools scope. The endpoint's 401 response advertises protected-resource metadata for authorization discovery.

Step 2 of 2 · Call the tool

Call a tool

{
  "jsonrpc": "2.0",
  "id": "tool-call-1",
  "method": "tools/call",
  "params": {
    "name": "social_twitch_user_schedule",
    "arguments": {
      "handle": "emongg"
    }
  }
}

Legacy MCP v1

Existing API-key clients can continue using the compatibility endpoint. New integrations should use MCP v2.

GET / POST /mcp/legacy

What can you do with this API?

Data explained and practical use cases

AI Guide

Question

What data can Twitch User Schedule provide, and how might I use it?

AI answer

Fetches a user's schedule by handle, returning a list of scheduled events with start time, end time, title, description, and thumbnail URL. Supports pagination via cursor and a trim option for lighter responses.

Data categoryDocumented fieldsHow to use them
RequesthandleProvide the required identifiers, filters, or paging inputs listed in the API document.
Responsedata.data, data.platform, data.resourceStatusInspect returned values and source references; availability depends on the request and upstream source.
  • Read the Returned Stream Schedule.
    • Prompt example: “Retrieve the schedule for [Twitch handle] and list its returned stream titles, start times and end times. Preserve supplied timezone information and distinguish missing schedule data from an empty schedule. Do not assume additional pages can be fetched.”
  • Find the Next Scheduled Stream.
    • Prompt example: “Retrieve the schedule for [Twitch handle] and show the next segment identified by the response with its start time. Keep this planned event separate from a currently live stream, and report an absent next segment without inventing a schedule.”
  • Check Schedule Cancellations and Interruptions.
    • Prompt example: “Retrieve the returned schedule for [Twitch handle] and identify segments marked cancelled, any cancellation-until value, and schedule interruptions. Keep these separate from ordinary scheduled start times; do not assume a missing schedule means the streamer is offline.”
  • Fit Scheduled Streams Into My Viewing Window.
    • Prompt example: “For [Twitch handle], compare returned schedule segment start and end times against [my viewing window and timezone]. Convert only timestamps with an explicit offset and flag ambiguous times. Exclude segments marked cancelled, retain unknown end times, and do not promise future streams beyond the returned schedule.”

These are suggested workflows, not completed lookups. Report missing, restricted, or partial data explicitly; verify the live response before making a decision.

Online test

Execute the current API with your API key and JSON payload. Online tests use this site's configured API environment; the Endpoint and copyable examples use the public integration address.

One request fetches one page. Copy nextCursor into cursor, or nextPage into page (1–11 for Reels), then run manually. Repeated requests may purchase data again. Completed lookups have a minimum charge of 10 credits, including cached, no-caption, private, restricted and not-found results. Resource status and actual billing status are independent; null credits are unknown, never free. Check usage.billingStatus, usage.chargedCredits and API usage records for the actual charge.

Try it

Send a real request with the same contract shown in the reference.

Endpoint
/social/twitch/user/schedule
MCP method
social_twitch_user_schedule
cURL
curl -X POST \
  https://api.nexscope.ai/social/twitch/user/schedule \
  -H "Authorization: Bearer nk-..." \
  -H "Content-Type: application/json" \
  -d '{ "handle": "emongg" }'
Request estimate: Estimating…Usage based. The final charge depends on actual usage. Estimating does not run the API or charge credits.API usage records
Response
No response yet. Run the request to see the response here.

Related APIs