# Twitch Channel Clips (`apt_marble/twitch-channel-clips`) Actor

Collect the top clips from any Twitch channel: titles, view counts, creators, dates, durations and links in one snapshot.

- **URL**: https://apify.com/apt\_marble/twitch-channel-clips.md
- **Developed by:** [Hamza](https://apify.com/apt_marble) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$1.50 / 1,000 clips

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Twitch Channel Clips

Paste one or more Twitch channel names and get back the top clips from each: titles, view counts, creators, dates, durations and links. Built for anyone who tracks what moments travel: talent scouts spotting viral creators, editors sourcing highlights, social teams finding clips to license or react to, and brands measuring which moments earned attention.

### What you can do with it

- **List a channel's top clips** — paste handles like `shroud` and get the most-watched moments back as clean rows.
- **Spot viral moments** — view counts rank the clips, and the creator field shows whose capture took off.
- **Slice by time window** — rank the last day, week or month, or all time; each window returns a different set.
- **Find superfans** — the creator behind each top clip is a highly engaged follower worth knowing.
- **Monitor moments on a schedule** — re-run the same channels and diff each fresh dataset against the last.

### What you get

One row per clip. Abridged sample of a single record:

```json
{
  "clipId": "TangentialBillowingJalapenoYee-ccA2oB1pEYh4CHWJ",
  "slug": "TangentialBillowingJalapenoYee-ccA2oB1pEYh4CHWJ",
  "title": "INSANE 1v3 clutch",
  "viewCount": 562198,
  "createdAt": "2023-06-02T11:41:50Z",
  "durationSeconds": 28.5,
  "clipUrl": "https://www.twitch.tv/shroud/clip/TangentialBillowingJalapenoYee-ccA2oB1pEYh4CHWJ",
  "thumbnailUrl": "https://clips-media-assets2.twitch.tv/…-preview.jpg",
  "game": "VALORANT",
  "curatorName": "pato_bolado",
  "curatorDisplayName": "Pato",
  "channelName": "shroud",
  "channelDisplayName": "shroud",
  "videoId": "1840501234",
  "videoOffsetSeconds": 120
}
```

### Input reference

| Setting | Type | Default | What it does |
| --- | --- | --- | --- |
| Channel names | list of text | — | Twitch channel names or channel links, e.g. `shroud` or `https://www.twitch.tv/shroud`. Clips are collected per channel. **Required.** |
| Time window | choice | `ALL_TIME` | Which clips to rank: the last day (`LAST_DAY`), week (`LAST_WEEK`) or month (`LAST_MONTH`), or all time (`ALL_TIME`). Each window returns a different set of top clips. |
| Clips per channel | whole number | `50` | How many top clips to collect per channel. Maximum 100. |
| Max items | whole number | `500` | Maximum clip rows across all channels. The actor works through your channels until this number is reached or the channels run out. Maximum 2,000. |

### Output fields

| Field | Type | Description |
| --- | --- | --- |
| `clipId` | text | Stable ID of the clip. |
| `slug` | text | Clip slug used in its link. |
| `title` | text | Clip title. |
| `viewCount` | number | Total views at collection time. |
| `createdAt` | text | When the clip was created (ISO date). |
| `durationSeconds` | number | Length in seconds. |
| `clipUrl` | text | Clean link to the clip page. |
| `thumbnailUrl` | text | Preview image. |
| `game` | text | Category the clip is filed under, when shown. |
| `curatorName` | text | Handle of the viewer who created the clip. |
| `curatorDisplayName` | text | Display name of the clip creator. |
| `channelName` | text | Clipped channel's handle. |
| `channelDisplayName` | text | Clipped channel's display name. |
| `videoId` | text | Source video ID, when linked. |
| `videoOffsetSeconds` | number | Seconds into the source video, when known. |

### Pricing

You pay per clip row, with no monthly minimum.

| What you are charged for | Price |
| --- | --- |
| Clip row — one row added to your dataset | **$1.50 per 1,000** |

### Limits & what this actor cannot do

- Each channel returns a single snapshot of up to 100 top clips per time window — the full clip history is not collected.
- Rows are a snapshot at the moment of collection; view counts keep changing afterwards.
- Fields a clip does not carry (source video, game) come back empty rather than guessed.
- Unknown or misspelled channel names are skipped, not charged.
- Speed depends on the size of the job and on Twitch's own response times; no fixed throughput is promised.
- Twitch's terms govern automated access. You are responsible for using the data lawfully and in line with the source site's terms, and for handling any personal data in line with applicable privacy law.

### FAQ

**Do I need a Twitch account?**
No. The actor reads only what Twitch shows on clip pages — paste channel names and press start.

**Which time window should I pick?**
All-time for the biggest proven moments, last week or month for what is hot now, last day for fresh breakouts.

**How many clips can I collect per run?**
Up to 100 per channel and 2,000 rows per run.

**Can I schedule it?**
Yes. Schedule it hourly, daily or weekly from the Apify console, and each run writes a fresh dataset you can compare against the last.

**Is the data complete?**
It covers the top clips of each channel for the chosen window at collection time. Clips below the snapshot cut-off are not included.

# Actor input Schema

## `channelNames` (type: `array`):

Twitch channel names or channel links, e.g. "shroud" or "https://www.twitch.tv/shroud". Clips are collected per channel.

## `timeWindow` (type: `string`):

Which clips to rank: the last day, week or month, or all time. Each window returns a genuinely different set of top clips.

## `maxClipsPerChannel` (type: `integer`):

How many top clips to collect per channel. Maximum 100 — each channel returns a single snapshot of its top clips.

## `maxItems` (type: `integer`):

Maximum clip rows to collect across all channels. The actor works through your channels until this number is reached or the channels run out.

## Actor input object example

```json
{
  "channelNames": [
    "https://www.twitch.tv/shroud"
  ],
  "timeWindow": "ALL_TIME",
  "maxClipsPerChannel": 50,
  "maxItems": 500
}
```

# Actor output Schema

## `results` (type: `string`):

Every row this run produced.

## `runSummary` (type: `string`):

What this run collected, and anything it could not read.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "channelNames": [
        "https://www.twitch.tv/shroud"
    ],
    "timeWindow": "ALL_TIME",
    "maxClipsPerChannel": 50,
    "maxItems": 500
};

// Run the Actor and wait for it to finish
const run = await client.actor("apt_marble/twitch-channel-clips").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "channelNames": ["https://www.twitch.tv/shroud"],
    "timeWindow": "ALL_TIME",
    "maxClipsPerChannel": 50,
    "maxItems": 500,
}

# Run the Actor and wait for it to finish
run = client.actor("apt_marble/twitch-channel-clips").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "channelNames": [
    "https://www.twitch.tv/shroud"
  ],
  "timeWindow": "ALL_TIME",
  "maxClipsPerChannel": 50,
  "maxItems": 500
}' |
apify call apt_marble/twitch-channel-clips --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,apt_marble/twitch-channel-clips"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/hUuLLZ4PBn3NUUfoY/builds/dVMjlllSE3LQGzG7B/openapi.json