# YouTube Channel Videos Scraper (`receptional_blender/youtube-channel-videos`) Actor

Pull every upload from any YouTube channel as clean structured rows — video ID, title, watch URL, view count, publish time, duration and thumbnail. Point it at a channel URL, an @handle or a UC... channel ID; powered by YouTube's own InnerTube API, so there's no Data API key and no headless browser.

- **URL**: https://apify.com/receptional\_blender/youtube-channel-videos.md
- **Developed by:** [Assia Fadli](https://apify.com/receptional_blender) (community)
- **Categories:** Videos
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.01 / 1,000 results

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/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## YouTube Channel Videos Scraper

**YouTube Channel Videos Scraper** turns any YouTube channel into a clean, structured list of its
uploads. Give it a channel URL, an `@handle`, or a `UC...` channel id and it returns one tidy row
per video — id, title, watch URL, view count, publish time, duration and thumbnail — ready to drop
into a spreadsheet, database or downstream pipeline.

No YouTube Data API key. No headless browser. No login. It talks directly to YouTube's own internal
**InnerTube** API (the same endpoints the website and apps use), so it's fast and lightweight.

Built for creators, analysts, agencies and developers who need a dependable feed of a channel's
videos without maintaining scraping infrastructure.

### What you get

One dataset row per video:

| Field | Description |
| --- | --- |
| `channelId` | The channel's `UC...` id |
| `channelTitle` | The channel's display name |
| `videoId` | 11-character video id |
| `title` | Video title |
| `url` | `https://www.youtube.com/watch?v=<videoId>` |
| `views` | View count text, e.g. `"191K views"` |
| `published` | Relative publish time, e.g. `"2 weeks ago"` |
| `duration` | Length, e.g. `"12:34"` |
| `thumbnail` | Highest-resolution thumbnail URL |

If the channel can't be read or has no public uploads, the actor still writes a single row with an
`error` field instead of failing with empty output.

### Input

| Field | Type | Required | Default | Description |
| --- | --- | --- | --- | --- |
| `channel` | string | ✅ | `https://www.youtube.com/@NASA` | Channel URL (`/@handle`, `/channel/UC...`, `/c/...`, `/user/...`), a bare `@handle`, or a `UC...` id |
| `maxResults` | integer | — | `50` | Maximum number of videos to return (fetched newest-first) |
| `language` | string | — | `en` | Interface language (`hl`) for YouTube's localized text |
| `proxyCountryCode` | string | — | `US` | ISO country code for the Apify residential proxy; leave blank to let Apify choose |

The original field names are all accepted, along with a few aliases (`channelUrl`/`url` for
`channel`, `maxVideos`/`limit` for `maxResults`, `proxyCountry` for `proxyCountryCode`, `hl` for
`language`).

#### Example input

```json
{
    "channel": "https://www.youtube.com/@NASA",
    "maxResults": 50,
    "proxyCountryCode": "US"
}
```

#### Example output row

```json
{
    "channelId": "UCLA_DiR1FfKNvjuUpBHmylQ",
    "channelTitle": "NASA",
    "videoId": "aRSBZN2UF0Q",
    "title": "Moon Base: June 2026 Update",
    "url": "https://www.youtube.com/watch?v=aRSBZN2UF0Q",
    "views": "191K views",
    "published": "2 weeks ago",
    "duration": "1:05",
    "thumbnail": "https://i.ytimg.com/vi/aRSBZN2UF0Q/hqdefault.jpg"
}
```

### How it works

1. **Resolve the channel.** If the input already contains a `UC...` id (bare or inside a `/channel/`
   URL) it is used directly. Otherwise the actor POSTs to `youtubei/v1/navigation/resolve_url` to
   turn an `@handle` / `/c/` / `/user/` reference into a `UC...` browse id.
2. **Browse the Videos tab.** It POSTs to `youtubei/v1/browse` with the channel's browse id and the
   `params` blob that selects the "Videos" tab. The channel-browse endpoint is served through the
   InnerTube **WEB** client (the ANDROID/IOS app clients return HTTP 400 there).
3. **Page through results.** It follows the `continuationCommand.token` from each response until
   `maxResults` is reached or there are no more pages, de-duplicating by `videoId` and guarding
   against continuation loops.

Requests are routed through Apify residential proxy when available, with an automatic fallback to a
direct connection.

### Pricing

This actor uses Apify's **pay-per-event** model. You're charged once per video delivered
(`video-scraped`); error rows are never billed, and the run stops automatically once your budget is
reached.

### Notes & limitations

- `views`, `published`, and `duration` are returned as YouTube's own display text (localized), not
  parsed numbers.
- Only regular uploads on the channel's **Videos** tab are returned (not Shorts, Live, Playlists or
  Podcasts).
- YouTube can change its internal API at any time; this actor tolerates several response shapes but
  is not covered by an official API contract.

### Tech

Written in **TypeScript** on the Apify SDK. HTTP-only, so builds are fast and runs are cheap.

### License

MIT © Assia Fadli

# Actor input Schema

## `channel` (type: `string`):

The YouTube channel to scrape. Accepts a channel URL (https://www.youtube.com/@NASA, /channel/UC..., /c/..., /user/...), a bare @handle (@NASA), or a UC... channel id.

## `maxResults` (type: `integer`):

How many videos to return at most. Uploads are collected newest-first in pages of about 30.

## `language` (type: `string`):

Optional interface language (hl) used when talking to YouTube, e.g. "en", "es", "fr". Affects the localized view/published/duration text. Defaults to English.

## `proxyCountryCode` (type: `string`):

Optional ISO country code for the Apify residential proxy (e.g. "US", "GB", "DE"). Leave blank to let Apify choose. If the proxy is unavailable the actor falls back to a direct request.

## Actor input object example

```json
{
  "channel": "https://www.youtube.com/@NASA",
  "maxResults": 50,
  "language": "en",
  "proxyCountryCode": "US"
}
```

# 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 = {
    "channel": "https://www.youtube.com/@NASA",
    "maxResults": 50,
    "language": "en",
    "proxyCountryCode": "US"
};

// Run the Actor and wait for it to finish
const run = await client.actor("receptional_blender/youtube-channel-videos").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 = {
    "channel": "https://www.youtube.com/@NASA",
    "maxResults": 50,
    "language": "en",
    "proxyCountryCode": "US",
}

# Run the Actor and wait for it to finish
run = client.actor("receptional_blender/youtube-channel-videos").call(run_input=run_input)

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

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

```

## CLI example

```bash
echo '{
  "channel": "https://www.youtube.com/@NASA",
  "maxResults": 50,
  "language": "en",
  "proxyCountryCode": "US"
}' |
apify call receptional_blender/youtube-channel-videos --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://mcp.apify.com/?tools=receptional_blender/youtube-channel-videos",
                "--header",
                "Authorization: Bearer <YOUR_API_TOKEN>"
            ]
        }
    }
}

```

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/acts/oGk40rjyYJ8kzC1iy/builds/yRLA9ipJs2o1AAvrT/openapi.json