YouTube Channel Details Scraper

Export public YouTube channel profile data from handles, channel IDs, or channel URLs.

Use this actor when you need a repeatable CSV, JSON, Excel, or API export of YouTube channel IDs, handles, subscriber/video/view counts, descriptions, links, country, joined date, avatars, banners, tags, topics, and section titles.

At a glance

• Input: YouTube channel URLs, handles, IDs, or custom URLs.
• Output: Channel identity, title, description, subscriber count, video count, view count, country, joined date, canonical URL, images, links, tags, topics, recent section titles, verification status, and errors.
• Controls: Maximum channels, recent section extraction, concurrency, and optional proxy.
• Best for: YouTube channel enrichment, creator research, lead generation, influencer lists, and YouTube channel API alternative workflows.
• No YouTube API key required: Uses public channel pages.

What can it do?

• Export YouTube channel details: Save channel IDs, handles, titles, descriptions, and canonical URLs.
• Collect public stats: Capture subscriber, video, and view counts when exposed.
• Find profile links: Save external links, avatars, banners, tags, topics, and country when available.
• Support lead workflows: Build structured creator, brand, or media prospect lists.
• Use as a YouTube Channel API alternative: Run from the Apify UI, API, schedules, webhooks, or the official Apify MCP server.

Common workflows

• Creator research: Enrich lists of YouTube handles with stats and links.
• Influencer discovery: Export public profile context for outreach qualification.
• Competitor monitoring: Track channel counts and profile changes over time.
• Media intelligence: Build structured channel datasets for research and reporting.
• AI-agent summaries: Let an agent fetch channel rows before comparing creators or niches.

Input example

{
  "channelUrlsOrHandles": [
    "@mkbhd",
    "https://www.youtube.com/@Google"
  ],
  "resumeChannelUrlsOrHandles": [],
  "maxChannels": 50,
  "includeRecentSections": true,
  "maxConcurrency": 3,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}

Output example

{
  "input": "@mkbhd",
  "channelUrl": "https://www.youtube.com/@mkbhd",
  "channelId": "UCBJycsmduvYEL83R_U4JriQ",
  "handle": "@mkbhd",
  "title": "Marques Brownlee",
  "description": "MKBHD: Quality Tech Videos...",
  "subscriberCountText": "19M subscribers",
  "subscriberCount": 19000000,
  "videoCountText": "1.7K videos",
  "videoCount": 1700,
  "viewCountText": "4B views",
  "viewCount": 4000000000,
  "country": "United States",
  "joinedDateText": "Joined Mar 21, 2008",
  "canonicalUrl": "https://www.youtube.com/@mkbhd",
  "avatarUrl": "https://yt3.googleusercontent.com/...",
  "bannerUrl": "https://yt3.googleusercontent.com/...",
  "externalLinks": [],
  "tags": ["tech", "reviews"],
  "topics": [],
  "recentSectionTitles": ["Videos", "Shorts"],
  "isVerified": true,
  "fetchedAt": "2026-07-03T10:00:00.000Z"
}

Tips for best results

• Use handles or full channel URLs when possible.
• Keep maxConcurrency moderate for large channel lists.
• Enable includeRecentSections when channel content structure matters.
• Use error to audit invalid, private, removed, or unavailable channels.
• Expect public counts to be rounded or abbreviated by YouTube.

Limits and caveats

• The actor exports public channel profile data only.
• It does not extract channel videos, comments, emails, private analytics, or subscriber lists.
• YouTube may hide or round counts and profile fields.
• Some channels may return partial rows or errors.

API usage

curl "https://api.apify.com/v2/acts/fetch_cat~youtube-channel-details-scraper/runs?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "channelUrlsOrHandles": ["@mkbhd"],
    "includeRecentSections": true
  }'

Node.js:

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('fetch_cat/youtube-channel-details-scraper').call({
  channelUrlsOrHandles: ['@mkbhd'],
  includeRecentSections: true,
});
console.log(run.defaultDatasetId);

Python:

from apify_client import ApifyClient

client = ApifyClient('MY-APIFY-TOKEN')
run = client.actor('fetch_cat/youtube-channel-details-scraper').call(run_input={
    'channelUrlsOrHandles': ['@mkbhd'],
    'includeRecentSections': True,
})
print(run['defaultDatasetId'])

MCP and AI agents

You can run this actor through the official Apify MCP server at https://mcp.apify.com.

For a focused single-actor tool, use:

https://mcp.apify.com?tools=fetch_cat/youtube-channel-details-scraper

Add it to Claude CLI:

claude mcp add apify-youtube-channel-details --transport http "https://mcp.apify.com?tools=fetch_cat/youtube-channel-details-scraper"

Or use this MCP JSON config:

{
  "mcpServers": {
    "apify-youtube-channel-details": {
      "url": "https://mcp.apify.com?tools=fetch_cat/youtube-channel-details-scraper"
    }
  }
}

Example prompts:

• "Get public channel details for @mkbhd and @Apify."
• "Compare subscriber and video counts for these YouTube channel URLs."
• "Export channel IDs, handles, country, joined date, and profile links for this creator list."

Agent-friendly inputs are channelUrlsOrHandles, resumeChannelUrlsOrHandles, maxChannels, includeRecentSections, maxConcurrency, and proxyConfiguration.

Support

If a run fails, returns no data, or a field looks wrong, open an issue from the Actor page.

Please include the Apify run ID or run URL, input JSON, one example public URL, query, or input item, what you expected, and what the dataset returned. Small reproducible inputs make parsing or site-layout issues much faster to fix.

Privacy and data handling

This Actor runs with Apify limited permissions and only processes data needed for the documented run. It uses content lookup inputs and public posts, profiles, videos, comments, or channel metadata needed for the requested output to produce the output dataset and sends requests to public Youtube Channel Details pages/endpoints; results are stored in Apify run storage for your account. FetchCat does not use your inputs or outputs for advertising, does not use them for model training, and does not retain them outside the Apify run except for transient support debugging when you explicitly share run details. You are responsible for using the Actor lawfully, respecting the target site's terms, and avoiding unnecessary personal or sensitive data in inputs.